Bug 2093051

Summary:	Nodes should reach OSUpdateStaged in a timely fashion needs to be more reliable
Product:	OpenShift Container Platform	Reporter:	David Eads <deads>
Component:	Test Framework	Assignee:	OpenShift Release Oversight <openshift-release-oversight>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.11	CC:	dgoodwin, openshift-release-oversight
Target Milestone:	---
Target Release:	4.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-04-30 18:04:53 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:

Description David Eads 2022-06-02 19:43:43 UTC

Failures like in https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.11-e2e-aws-upgrade/1532346119462326272, I found that we don't have a backstop value for osupdatestaged. If we complete the upgrade, then at some point we were OSUpdateStaged even if we didn't observe that event

Comment 2 Rory Thrasher 2024-04-30 18:04:53 UTC

OCP is no longer using Bugzilla and this bug appears to have been left in an orphaned state. If the bug is still relevant, please open a new issue in the OCPBUGS Jira project: https://issues.redhat.com/projects/OCPBUGS/summary