Bug 1804600

Summary: oc image mirror doesn't mirror manifestlist for single image manifestlists
Product: OpenShift Container Platform Reporter: Maciej Szulik <maszulik>
Component: OLMAssignee: Kevin Rizza <krizza>
OLM sub component: OLM QA Contact: Jian Zhang <jiazha>
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: urgent CC: agawand, ansverma, aos-bugs, bparees, ecordell, elalance, jiazha, jkaur, jokerman, jrfuller, krizza, maszulik, mfojtik, mzali, nhale, pweil, qitang, rkant, shurley, susuresh
Version: 4.4Keywords: Reopened
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1800674 Environment:
Last Closed: 2020-05-04 11:37:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1800674    
Bug Blocks: 1804463    

Comment 1 Maciej Szulik 2020-02-19 09:11:54 UTC
4.4 cherry-pick in https://github.com/openshift/oc/pull/304

Comment 5 Kevin Rizza 2020-02-24 15:14:19 UTC
Hi Jian,

I would expect the error you saw. `oc adm catalog mirror` isn't supposed to work against any image. It only works against operator-registry catalog images because it reads the contents of the database and mirrors the related images. This fix was to update `oc image mirror` which `oc adm catalog mirror` calls internally to mirror the related images in the database.

I think that testing `oc image mirror` against a manifest that contains just one architecture should be enough to verify this bug. If you wanted to double check that `oc adm catalog mirror` is consuming image mirror's latest behavior as well, you could just mirror the normal catalog and compare the digests that `oc adm catalog mirror` is trying to copy over to what you already saw when running `oc adm image mirror`.

Comment 8 errata-xmlrpc 2020-05-04 11:37:31 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-2020:0581