Bug 2093051 - Nodes should reach OSUpdateStaged in a timely fashion needs to be more reliable
Summary: Nodes should reach OSUpdateStaged in a timely fashion needs to be more reliable
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Test Framework
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.11.0
Assignee: OpenShift Release Oversight
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-02 19:43 UTC by David Eads
Modified: 2024-04-30 18:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-30 18:04:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 27206 0 None open bug 2093051: use the node update finished as a backup completion time for OSStaged 2022-06-02 19:44:05 UTC

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
Note You need to log in before you can comment on or make changes to this bug.