Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1885322 - [sig-cluster-lifecycle] cluster upgrade should be fast
Summary: [sig-cluster-lifecycle] cluster upgrade should be fast
Keywords:
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 4.6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: aos-team-ota
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On: 1929650 1879099
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-05 15:33 UTC by Kelvin Fan
Modified: 2021-07-27 16:59 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1929650 (view as bug list)
Environment:
[sig-cluster-lifecycle] cluster upgrade should be fast
Last Closed:
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. 
https://issues.redhat.com/browse/OTA-340

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.


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