Bug 1870344 - [sig-cluster-lifecycle] Cluster version operator acknowledges upgrade
Summary: [sig-cluster-lifecycle] Cluster version operator acknowledges upgrade
Keywords:
Status: CLOSED DUPLICATE of bug 1843505
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 4.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.6.0
Assignee: Over the Air Updates
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-19 20:19 UTC by David Eads
Modified: 2022-05-06 12:29 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
[sig-cluster-lifecycle] Cluster version operator acknowledges upgrade
Last Closed: 2020-08-25 17:22:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description David Eads 2020-08-19 20:19:26 UTC 
test:
[sig-cluster-lifecycle] Cluster version operator acknowledges upgrade 

is failing frequently in CI, see search results:
https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-cluster-lifecycle%5C%5D+Cluster+version+operator+acknowledges+upgrade

In the last seven days, this appears to have failed on about 10% of AWS upgrades.  On all other platforms, it's practically gone, but AWS upgrades are heavily impacted.


This is a link to the latest one: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.5-stable-to-4.6-ci/1296014686348644352
Comment 1 W. Trevor King 2020-08-19 20:26:55 UTC 
Might be a dup of bug 1843505.
Comment 2 Lalatendu Mohanty 2020-08-21 18:49:47 UTC 
Moving to the next sprint as today is the end of sprint.
Comment 3 W. Trevor King 2020-08-25 17:22:19 UTC 
I'm just going to close this as a dup of bug 1843505.  We can re-open if it's still happening after the remaining PR for bug 1843505 has landed.

*** This bug has been marked as a duplicate of bug 1843505 ***
Note You need to log in before you can comment on or make changes to this bug.