Bug 1813361
| Summary: | CI: deployment error: more unauth image pulls with image change triggers | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Gabe Montero <gmontero> | |
| Component: | openshift-controller-manager | Assignee: | Gabe Montero <gmontero> | |
| Status: | CLOSED ERRATA | QA Contact: | wewang <wewang> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.5 | CC: | aos-bugs, mfojtik, obulatov | |
| Target Milestone: | --- | |||
| Target Release: | 4.5.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: the local ref setting on imagestreams can be ignored if imagestream access occurs very soon after cluster startup or restart of the openshift controller manager because the openshift controller manager might have stale imagestreams its cache with incomplete metadata
Consequence: if the imagestream was backed by a private registry which the internal image registry had credentials for, but the consumer did not have credentials for, the subsequent image pull would fail
Fix: the openshift controller manager was updated to refresh its imagestream cache if it was apparent the metadata initialization was incomplete
Result: local ref imagestream policy is preserved even during the timing windows that occur immediately after cluster start or openshift controller manager restart
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1813419 1813420 (view as bug list) | Environment: | ||
| Last Closed: | 2020-07-13 17:19:58 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1813419 | |||
|
Description
Gabe Montero
2020-03-13 15:25:10 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409 |