Bug 1737120 - multi-arch builds failing because image-references contains stale images
Summary: multi-arch builds failing because image-references contains stale images
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.2.0
Assignee: Antonio Murdaca
QA Contact: Micah Abbott
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-02 17:13 UTC by Antonio Murdaca
Modified: 2019-10-16 06:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:34:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 1028 0 None None None 2019-08-02 17:14:58 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:34:42 UTC

Description Antonio Murdaca 2019-08-02 17:13:51 UTC 
Description of problem:

multi-arch builds are failing because we have stale images in image-references. That came as part of a big feature where the MCO folded all images into one.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Antonio Murdaca 2019-08-02 17:14:44 UTC 
https://github.com/openshift/machine-config-operator/pull/1028
Comment 3 Michael Nguyen 2019-08-21 18:22:40 UTC 
Considering this verified based on this comment by the multi-arch team:
https://github.com/openshift/machine-config-operator/pull/1028#issuecomment-517758473
Comment 4 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
Note You need to log in before you can comment on or make changes to this bug.