Bug 1832344
| Summary: | After upgrade, openshift-samples is moving between ready and "Progressing" status | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Gabe Montero <gmontero> |
| Component: | Samples | Assignee: | Gabe Montero <gmontero> |
| Status: | CLOSED ERRATA | QA Contact: | XiuJuan Wang <xiuwang> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.4 | CC: | adam.kaplan, apolak, cajieh, gmontero, hongkliu, jlee, jnaess, obulatov, rgregory, scuppett, wking, xiuwang |
| Target Milestone: | --- | Keywords: | Upgrades |
| Target Release: | 4.4.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: if a sample template available in a prior release was removed in a subsequent release, then during upgrade to that subsequent release the removed template could be incorrectly tracked as needing to be updated, and the subsequent failure to read that template from the current payload leads to confusing 'no such file or directory error reading file []' messsages and apiserver errors reported in the samples clusteroperator status
Consequence: overall upgraded could be marked as failed if the problematic timing windows in samples operator occurred
Fix: samples operated was updated to not attempt to update templates which existed in a prior release but not in the release we are upgrading to
Result: templates that are removed release to release should not cause samples operator to fail upgrade or report confusing clusteroperator status
|
Story Points: | --- |
| Clone Of: | 1828065 | Environment: | |
| Last Closed: | 2020-06-02 11:18:33 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: | 1828065 | ||
| Bug Blocks: | 1841996 | ||
|
Comment 1
Vadim Rutkovsky
2020-05-06 15:59:03 UTC
Bumping to high because anything that improves signal to noise ratio after upgrades is worthy of high. Can't reproduce this issue when upgrade from 4.3.0-0.nightly-2020-05-24-223407 to 4.4.0-0.nightly-2020-05-25-020741 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:2310 *** Bug 1842901 has been marked as a duplicate of this bug. *** |