The problem:

The status loop is triggered in the command `run` when `–watch` is set. Status loop is responsible to gather information from aggregator server and report to stdout.

Currently the loop is not considering pod status, and aggregator server sometimes takes too long to report failure in the environment, and timeout the pods.

 Expected results: OPCT/CLI detects when pods is in failed state for some time (maybe 10 minutes) and fail the execution, instead of running forever.

Additional information:

OPCT-300 has been created to provide more information about pods status when aggregator has no information about pod progress yet, it could happen in some cases, such as:

• pod is in very in initial state, taking some time to initialize the progress report module
• pod failed to initialize and will never report progress to aggregator server

The PR 118[1] covers the first bullet.

[1] https://github.com/redhat-openshift-ecosystem/provider-certification-tool/pull/118