Bug 1784317
Summary: | ImportImageErrorsExist keeps true while no import error in openshift-samples clusteroperator. | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | XiuJuan Wang <xiuwang> |
Component: | Samples | Assignee: | Gabe Montero <gmontero> |
Status: | CLOSED ERRATA | QA Contact: | XiuJuan Wang <xiuwang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.3.0 | CC: | gmontero |
Target Milestone: | --- | ||
Target Release: | 4.3.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: if samples operator was provided an invalid samplesRegistry override, leading to failed imagestream imports, the samples operator would take a very very long time to ignore errors from the invalid setting and reach a clean state even after the samplesRegistry override was corrected by the user
Consequence: the samples operator would incorrectly report degraded for long stretches even after an invalid samplesRegistry setting was fixed
Fix: the samples operator now properly clears out pending state on imagestreamimports when the samplesRegistry override is changed
Result: the samples operator will recover in a timely fashion when and invalid samplesRegistry override is corrected.
|
Story Points: | --- |
Clone Of: | 1784315 | Environment: | |
Last Closed: | 2020-03-10 23:52:55 UTC | Type: | --- |
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: | 1784315 | ||
Bug Blocks: |
Description
XiuJuan Wang
2019-12-17 08:49:11 UTC
waiting on 4.3.z to open up so https://github.com/openshift/cluster-samples-operator/pull/219 can be associated with it Test with 4.3.0-0.nightly-2020-02-20-190050 ImportImageErrorsExist could been clean after the the import error disappeared a while. Mark this bug as verified. 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:0676 |