Bug 1970969 - test '[sig-cluster-lifecycle] cluster upgrade should be fast' has no units of measurement
Summary: test '[sig-cluster-lifecycle] cluster upgrade should be fast' has no units of...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Test Infrastructure
Version: 4.8
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.8.z
Assignee: Zack Zlotnik
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-11 15:03 UTC by Zack Zlotnik
Modified: 2022-04-13 15:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-13 15:44:02 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 26207 0 None open clarify failure message 2021-06-11 15:03:29 UTC

Description Zack Zlotnik 2021-06-11 15:03:29 UTC
Description of problem:

I'm not sure if this is the correct BZ queue for this; please feel free to move if not.

The test "[sig-cluster-lifecycle] cluster upgrade should be fast" does not specify a unit of measurement upon failure, nor does it specify what "fast" means in this context. Adding the word "minutes" and the timeout value to the output would help those who see this test fail.

Version-Release number of selected component (if applicable):


How reproducible:

Whenever "[sig-cluster-lifecycle] cluster upgrade should be fast" fails.

Steps to Reproduce:
1.
2.
3.

Actual results:

upgrade to registry.build01.ci.openshift.org/ci-op-h21l7wld/release@sha256:2148b1c121946ac4f186bb22b166247d3df0ad9cf3966f05dc2a6ea27bc53927 took too long: 86.33481681223333

Expected results:

upgrade to registry.build01.ci.openshift.org/ci-op-h21l7wld/release@sha256:2148b1c121946ac4f186bb22b166247d3df0ad9cf3966f05dc2a6ea27bc53927 took too long: 86.3 minutes, expected 75 minutes or less

Additional info:

https://github.com/openshift/origin/pull/26207


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