Bug 1885322 - [sig-cluster-lifecycle] cluster upgrade should be fast
Summary: [sig-cluster-lifecycle] cluster upgrade should be fast
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.z
Assignee: David Hurta
QA Contact: Johnny Liu
Depends On: 1929650
TreeView+ depends on / blocked
Reported: 2020-10-05 15:33 UTC by Kelvin Fan
Modified: 2022-11-23 13:13 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1929650 (view as bug list)
[sig-cluster-lifecycle] cluster upgrade should be fast
Last Closed: 2022-11-21 19:18:33 UTC
Target Upstream Version:

Attachments (Terms of Use)

Comment 1 Michael McCune 2020-10-05 18:07:58 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

Comment 2 Scott Dodson 2020-11-09 20:14:05 UTC
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.

Comment 4 Pratik Mahajan 2021-01-26 17:58:14 UTC
We are gonna do some analysis and look for improvements. 

Comment 6 W. Trevor King 2021-07-02 22:39:08 UTC
Not much we can do here without some master-ward progress besides bumping the origin timeout.

Comment 7 Lalatendu Mohanty 2021-10-06 17:22:16 UTC
We back port the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1942164 i.e.increase in timeout to 90mins.

Comment 9 Devan Goodwin 2022-03-14 17:05:11 UTC
Bug hanging open and likely needs to be closed. This test doesn't seem to exist anymore.

Comment 10 David Hurta 2022-03-16 10:59:38 UTC
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.

Comment 11 Vikas Laad 2022-11-21 19:18:33 UTC
OCP 4.7 is EOL now https://access.redhat.com/errata/RHBA-2022:7334

Closing all the open bugs.

Note You need to log in before you can comment on or make changes to this bug.