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