Bug 1838375
| Summary: | Failed the catalog image build with "error: unable to parse image registry.redhat.io/openshift4/ose-operator-registry:v4.3: unknown image manifest of type *manifestlist.DeserializedManifestList from manifest" | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Daein Park <dapark> |
| Component: | OLM | Assignee: | Evan Cordell <ecordell> |
| OLM sub component: | OLM | QA Contact: | Jian Zhang <jiazha> |
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | aos-bugs, arghosh, aslevi, bluddy, jiho, jmalde, jokerman, mas-hatada, mfojtik, mfuruta, rh-container, vdinh |
| Version: | 4.3.z | ||
| Target Milestone: | --- | ||
| Target Release: | 4.6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-28 17:23:46 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: | |||
Dear Red Hat, We also encountered this issue, and currently we cannot deploy/upgrade Operators on disconnected env due to this issue. It's a critical issue for disconnected env, so we would like Red Hat to fix this issue as soon as possible. Best Regards, Masaki Hatada Hello, The same error also appears in our environment. we would appreciate your help as soon as possible. Thanks, Asaf We faced the same issue with oc version 4.3.19
oc adm catalog build command [1] fails with error:
error: unable to parse image registry.redhat.io/openshift4/ose-operator-registry:v4.3: unknown image manifest of type *manifestlist.DeserializedManifestList from manifest sha256:34588f4b73e97b6fb96fcdf01ecfc0986ebb51b7965b94e7aee88a184be2efdf
[1] $ oc adm catalog build \
--appregistry-org redhat-operators \
--from=registry.redhat.io/openshift4/ose-operator-registry:v4.3 \
--to=<registry_host_name>:<port>/olm/redhat-operators:v1 \
We took out the --from flag as a workaround for now
The latest 4.3 z-stream images have multi-arch manifest lists, so they can't be used as a base image. The --filter-by-os option can be used to select the target architecture -- see my comment that mentions the same issue here: https://bugzilla.redhat.com/show_bug.cgi?id=1833422#c2. There's an in-progress change to oc that will provide a default value of adm64/linux for the --filter-by-os option: https://github.com/openshift/oc/pull/423/. Closing this because there is a workaround (`--filter-by-os`) and a fix being tracked in a separate BZ. If there is additional help needed please re-open, or open a new bug if the scope is different from what was described here. |
Description of problem: Failed the catalog image building command[0] with "error: unable to parse image registry.redhat.io/openshift4/ose-operator-registry:v4.3: unknown image manifest of type *manifestlist.DeserializedManifestList from manifest sha256:...". [0] Building an Operator catalog image [ https://docs.openshift.com/container-platform/4.3/operators/olm-restricted-networks.html#olm-building-operator-catalog-image_olm-restricted-networks ] ~~~ $ oc adm catalog build \ --appregistry-org redhat-operators \ --from=registry.redhat.io/openshift4/ose-operator-registry:v4.3 \ --to=<registry_host_name>:<port>/olm/redhat-operators:v1 \ [-a ${REG_CREDS}] \ [--insecure] ~~~ Version-Release number of selected component (if applicable): I could verified to reproduce this issue on the 4.3.9, 4.3.13, 4.3.20 client version. How reproducible: You can always reproduce this issue through above "oc adm catalog build". Steps to Reproduce: 1. 2. 3. Actual results: Failed building the operator catalog image and customers cannot use Operator Lifecycle Manager on OCP4.z installed on restricted networks. Expected results: Successful building the operator catalog image and pushing the image to the private registry. Additional info: If I use the oc v4.4.4 and v4.4 image tag for building catalog image, it was successful.