Description of problem: e2e-aws-scaleup-rhel7 test was added to the MCO repo recently (https://github.com/openshift/release/pull/4800) and it has not had a passing run yet, see https://prow.svc.ci.openshift.org/job-history/origin-ci-test/pr-logs/directory/pull-ci-openshift-machine-config-operator-master-e2e-aws-scaleup-rhel7 While this is not a blocking test : Is it a good use of resources to run a test that always fails? It's also confusing to see this on PRs as the history is all red. Poking through the results I've seen this error a few times: ``` fatal: [10.0.158.230]: FAILED! => changed=false msg: |- Unable to install cri-o, openshift-clients, openshift-hyperkube. Please ensure repos are configured properly to provide these packages and indicated versions. ``` Is there a fix in the works? Steps to Reproduce: 1. let test run in test suite 2. note that it fails Actual results: fails Expected results: pass
Changing to Installer team as they added the test to MCO repo and elsewhere (see https://jira.coreos.com/browse/CORS-1059)
When openshift-clients was removed from the origin repo a couple of days ago, this test started failing. https://github.com/openshift/release/pull/4873 A fix is in the works here, https://github.com/openshift/release/pull/4903
Per the fix PR, this is not some installer issue, move back to "Test Suite"
Going to mark this verified. The jobs are not failing due to the RPM issues.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922