Bug 1737086

Summary: machine-api-operator caused nightly builds to fail August 1 2019
Product: OpenShift Container Platform Reporter: Peter Hunt <pehunt>
Component: Cloud ComputeAssignee: Julia Kreger <jkreger>
Status: CLOSED ERRATA QA Contact: Jianwei Hou <jhou>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: agarcial, rbryant, rpittau, xtian
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: buildcop
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 06:34:33 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 Peter Hunt 2019-08-02 14:45:41 UTC
Description of problem:
machine-api-operator caused 4.2.0 nightly build to fail with the following error:
machine-api-operator contained an invalid image-references file

Version-Release number of selected component (if applicable):
4.2.0-nightly

How reproducible:
reproduced twice

Additional info:
https://openshift-release.svc.ci.openshift.org/releasestream/4.2.0-0.nightly/release/4.2.0-0.nightly-2019-08-02-002417
and 
https://openshift-release.svc.ci.openshift.org/releasestream/4.2.0-0.nightly/release/4.2.0-0.nightly-2019-08-02-075256

Comment 1 Russell Bryant 2019-08-02 14:52:59 UTC
This PR should resolve a build failure that occurred with ART, but not in OpenShift CI

https://github.com/openshift/ironic-image/pull/10

Comment 2 Julia Kreger 2019-08-02 15:47:29 UTC
Pull https://github.com/openshift/ironic-image/pull/12 created to get the fix to the 4.2-release branch.

Comment 4 Jianwei Hou 2019-08-12 05:44:45 UTC
I've managed to get newer nightly builds, so I think this is no longer blocking the builds.

Comment 5 errata-xmlrpc 2019-10-16 06:34:33 UTC
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