Bug 2032434

Summary:	[RFE] Add necessary features to Openshift Integrated Registry to be used as disconnected registry for OCP releases and OLM Images
Product:	OpenShift Container Platform	Reporter:	Juan Manuel Parrilla Madrid <jparrill>
Component:	Image Registry	Assignee:	Oleg Bulatov <obulatov>
Status:	CLOSED NOTABUG	QA Contact:	XiuJuan Wang <xiuwang>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.9	CC:	aos-bugs, kkarampo, mavazque, oarribas
Target Milestone:	---
Target Release:	---
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:	2021-12-14 14:05:05 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 Juan Manuel Parrilla Madrid 2021-12-14 13:56:04 UTC

Description of problem:

When you enables the Openshift internal registry (integrated) to be 'Managed' it deploys a pod which holds an internal registry. This can be used by the OCP users to upload their images but it cannot be used as a Openshift Internal Registry to host:

- OCP Releases
- OLM Images

The technical reasons are:

- the registry doesn't support manifest lists (fat manifests)
- you cannot push manifest without a tag

This will be very useful for Edge cases like Telco and others.

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

OCP 4.9 and earlier

How reproducible:

Always

Steps to Reproduce:

1. Enables the Integrated Registry (Managed) into the OCP Cluster config ([https://docs.openshift.com/container-platform/4.9/registry/configuring_registry_storage/configuring-registry-storage-baremetal.html](https://docs.openshift.com/container-platform/4.9/registry/configuring_registry_storage/configuring-registry-storage-baremetal.html))
2. Execute the commands to perform the sync (down bellow)
3. Wait until if fails (this does not fail at the beggining

Actual results:

Commands executed:

---

OLM_DESTINATION_INDEX=[default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/redhat-operator-index:v4.9](http://default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/redhat-operator-index:v4.9)
DESTINATION_REGISTRY=[default-route-openshift-image-registry.apps.test-ci.alklabs.com](http://default-route-openshift-image-registry.apps.test-ci.alklabs.com/)
OLM_DESTINATION_REGISTRY_IMAGE_NS=olm

## oc adm catalog mirror ${OLM_DESTINATION_INDEX} ${DESTINATION_REGISTRY}/${OLM_DESTINATION_REGISTRY_IMAGE_NS} --registry-config=${PULL_SECRET}

## Many errors

error: unable to push manifest to [default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/openshift4-ose-kubernetes-nmstate-handler-rhel8:](http://default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/openshift4-ose-kubernetes-nmstate-handler-rhel8:) received unexpected HTTP status: 500 Internal Server Error
error: unable to push manifest to [default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/openshift4-ose-kubernetes-nmstate-handler-rhel8:](http://default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/openshift4-ose-kubernetes-nmstate-handler-rhel8:) received unexpected HTTP status: 500 Internal Server Error
error: unable to push manifest to [default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/openshift4-ose-csi-external-provisioner-rhel8:c4b69a85:](http://default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/openshift4-ose-csi-external-provisioner-rhel8:c4b69a85:) manifest invalid: manifest invalid
error: unable to push manifest to [default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/openshift4-ose-csi-external-attacher:7e5d8214:](http://default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/openshift4-ose-csi-external-attacher:7e5d8214:) manifest invalid: manifest invalid
error: unable to push manifest to [default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/openshift4-ose-csi-external-attacher:27ae2b3d:](http://default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/openshift4-ose-csi-external-attacher:27ae2b3d:) manifest invalid: manifest invalid
error: unable to push manifest to [default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/openshift4-ose-csi-external-attacher:3bbeb5c5:](http://default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/openshift4-ose-csi-external-attacher:3bbeb5c5:) manifest invalid: manifest invalid
error: unable to push manifest to [default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/openshift4-ose-kubernetes-nmstate-handler-rhel8:d2182ee2:](http://default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/openshift4-ose-kubernetes-nmstate-handler-rhel8:d2182ee2:) manifest invalid: manifest invalid
error: unable to push manifest to [default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/ocs4-ocs-rhel8-operator:](http://default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/ocs4-ocs-rhel8-operator:) received unexpected HTTP status: 500 Internal Server Error
error: unable to push manifest to [default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/ocs4-ocs-rhel8-operator:](http://default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/ocs4-ocs-rhel8-operator:) received unexpected HTTP status: 500 Internal Server Error
error: unable to push manifest to [default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/ocs4-ocs-rhel8-operator:](http://default-route-openshift-image-registry.apps.test-ci.alklabs.com/olm/ocs4-ocs-rhel8-operator:) received unexpected HTTP status: 500 Internal Server Error

---

Expected results:

Mirroring performed properly

Additional info:

Comment 2 Oleg Bulatov 2021-12-14 14:05:05 UTC

We don't track features nor RFEs in Bugzilla. RFEs are tracked at https://issues.redhat.com/projects/RFE