Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Normal
Fix Version/s: None
Affects Version/s: 4.13.z, 4.12.z, 4.11.z, 4.10.z, 4.14
Component/s: Documentation / Image Registry
Labels:
- easy-fix
- triaged

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
4
Severity:
Moderate
Regression:
No

Target Backport Versions:
None
Target Version:
None
Release Blocker:
None
Sprint:
OSDOCS Sprint 239
sprint_count:
1

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

The documentation for using an ObjectBucketClaim for image-registry storage indicates that the OBC should be created in the openshift-storage namespace. However, this does not work. The OBC should be created in the oepnshift-image-registry namespace (our DO370 training uses the correct namespace).

Version-Release number of selected component (if applicable):

How reproducible:

Follow the docs as written

Steps to Reproduce:

1. Create the OBC in the openshift-storage namespace
2. Configure the image-registry to use the OBC
3. View authentication errors in the logs

Actual results:

OBC is not used for iamge-registry data

Expected results:

OBC should work

Additional info:

Assignee:: Steven Smith

Reporter:: Matthew Secaur

Need Info From:: None

Contributors:: None

QA Contact:: XiuJuan Wang

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2023/06/01 2:59 PM

Updated:: 2025/07/26 11:50 AM

Resolved:: 2023/07/25 3:46 PM