The CLI is not updating the progress when running the v0.2+ on 4.12.

While 4.12 is not GA yet, I am setting this card to the v0.3 development.

Steps to reproduce:

• Install 4.12 cluster (4.12.0-rc.4)
• Setup the Certification environment (set node label and taints, registry, etc)
• Download and run the v0.2+ OPCT
• run: $ ./openshift-provider-cert-linux-amd64-v0.2.0 run -w;
• (check the progress [field MESSAGE] will not be updated)
• Check the log of pod 'sonobuoy-20-openshift-conformance-validated-job-<id>', and container 'report-progress', and check that nothing is read
• Check the log of the container 'plugin' and check the openshift-tests publishing messages on the stdout (and writing to pipe file)
• Install a cluster in an older version (<=4.11), run the same OPCT version and check the progress being updated, and report-progress reading the pipe messages

Note:

• This problem is not causing the crash on the tool, only in the update progress engine.
• The tool has the ability to signilze when the execution is finished, gracefully shutdown the job

Possible cause:

• the file pipe used to capture the stdout for openshift-tests is not being read by report-progress, responsible to parse the data and send to the sonobuoy aggregator
• SCC could be blocking the file pipe usage? Why only in 4.12?