Bug 1811143
| Summary: | upgrades where entire sample imagestreams were removed in the new version can get stuck in progressing | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Gabe Montero <gmontero> | |
| Component: | Samples | Assignee: | Gabe Montero <gmontero> | |
| Status: | CLOSED ERRATA | QA Contact: | XiuJuan Wang <xiuwang> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.4 | CC: | wking | |
| Target Milestone: | --- | Keywords: | Upgrades | |
| Target Release: | 4.5.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: if a sample imagestream available in a prior release was removed in a subsequent release, then during upgrade to that subsequent release the removed imagestream could be incorrectly tracked as needing imagestreamimports to complete, and since no imagestreamimmports are even occurring, samples will not report its upgrade as complete
Consequence: overall upgraded would be marked as failed if the problematic timing windows in samples operator occured
Fix: samples operated was updated to not attempt to track imagestreams which existed in a prior release but not in the release we are upgrading to
Result: imagestreams that are removed release to release should not cause samples operator to fail upgrade
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1811204 1811206 (view as bug list) | Environment: | ||
| Last Closed: | 2020-07-13 17:18:56 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: | 1811204 | |||
|
Description
Gabe Montero
2020-03-06 17:25:12 UTC
Gabe thanks I tried to upgrade from 4.2.23 to 4.3，don't met the bug issue. I must have missed the chance to reproduce it as you said. Upgrade from 4.4.0-rc.0 to 4.5.0-0.nightly-2020-03-16-004817 successfully, we are good to mark this bug to verified. Cross-linking bug 1828065, which is also about 4.5 samples Progessing. 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 |