Bug 1970969

Summary:	test '[sig-cluster-lifecycle] cluster upgrade should be fast' has no units of measurement
Product:	OpenShift Container Platform	Reporter:	Zack Zlotnik <zzlotnik>
Component:	Test Infrastructure	Assignee:	Zack Zlotnik <zzlotnik>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	4.8	CC:	bleanhar
Target Milestone:	---
Target Release:	4.8.z
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:	2022-04-13 15:44:02 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 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