Bug 1885322
| Summary: | [sig-cluster-lifecycle] cluster upgrade should be fast | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Kelvin Fan <kfan> | |
| Component: | Cluster Version Operator | Assignee: | David Hurta <dhurta> | |
| Status: | CLOSED EOL | QA Contact: | Johnny Liu <jialiu> | |
| Severity: | low | Docs Contact: | ||
| Priority: | low | |||
| Version: | 4.6 | CC: | aos-bugs, bleanhar, dgoodwin, dhurta, lmohanty, mimccune, pmahajan, stbenjam, vlaad, wking, yanyang | |
| Target Milestone: | --- | |||
| Target Release: | 4.7.z | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1929650 (view as bug list) | Environment: |
[sig-cluster-lifecycle] cluster upgrade should be fast
|
|
| Last Closed: | 2022-11-21 19:18:33 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: | 1929650 | |||
| Bug Blocks: | ||||
|
Description
Kelvin Fan
2020-10-05 15:33:55 UTC
i looked at the test in question which failed[0] and it seems like a wrapper around the upgrade process. i think we need more investigation on this issue, especially considering that in the prow job linked there are flaky network tests (which could also lead to a slow upgrade if there was network instability). i'm not convinced this is specifically a cloud compute problem. [0] https://github.com/openshift/origin/blob/master/test/e2e/upgrade/upgrade.go#L389 I agree this likely isn't Cloud, the most promising is probably seeing fixes for https://bugzilla.redhat.com/show_bug.cgi?id=1879099 Anyway, OTA team can shepherd this along more effectively than the cloud team. We are gonna do some analysis and look for improvements. https://issues.redhat.com/browse/OTA-340 Not much we can do here without some master-ward progress besides bumping the origin timeout. We back port the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1942164 i.e.increase in timeout to 90mins. Bug hanging open and likely needs to be closed. This test doesn't seem to exist anymore. To my knowledge, the test is still being run in some of the periodic CI jobs. Please, correct me if I am wrong. For the jobs containing the test see: https://prow.ci.openshift.org/?job=*4.7-upgrade-from*ovn-upgrade* Currently, in the jobs, this test can be found named as `[sig-cluster-lifecycle] cluster upgrade should be fast` I have looked in some of the jobs histories, and the test mostly passes but can be seen reaching near the current 75 minutes mark. And occasionally, the test still fails: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.7-upgrade-from-stable-4.6-e2e-aws-ovn-upgrade/1501971273553547264 (upgrade took ~77 minutes) https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.7-upgrade-from-stable-4.6-e2e-gcp-ovn-upgrade/1499825345673564160 (upgrade took ~76 minutes) https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.7-upgrade-from-stable-4.6-e2e-gcp-ovn-upgrade/1491487489104285696 (upgrade took ~76 minutes) The Pull Request https://github.com/openshift/origin/pull/26878 for the backport is open and waiting for a review. OCP 4.7 is EOL now https://access.redhat.com/errata/RHBA-2022:7334 Closing all the open bugs. |