Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1821427

Summary:	Removing internal registry does not remove internalRegistryHostname
Product:	OpenShift Container Platform	Reporter:	Scott Seago <sseago>
Component:	Image Registry	Assignee:	Ricardo Maraschini <rmarasch>
Status:	CLOSED ERRATA	QA Contact:	Wenjing Zheng <wzheng>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2.z	CC:	aos-bugs, rmarasch
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Setting the image registry as removed Consequence: Image registry hostname was still present on image config status. Fix: Removing the image registry hostname from image config when the image registry is removed. Result: Image registry hostname is not presented on image config status when there is no image registry available.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:25:52 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 Scott Seago 2020-04-06 19:42:46 UTC

Description of problem:
When setting spec.managementState in configs.imageregistry.operator.openshift.io/cluster to "Removed", the internalRegistryHostname is not removed from image.config.openshift.io/cluster or from the openshift-apiserver config configmap.

Version-Release number of selected component (if applicable): 4.2.x and 4.3.1 (seen in both)


How reproducible:
Always

Steps to Reproduce:
1. Set managementState to "Removed" in configs.imageregistry.operator.openshift.io/cluster

Actual results:
image.config.openshift.io/cluster still has Status.internalRegistryHostname configured, and the openshift-apiserver configmap config still has imagePolicyConfig.internalRegistryHostname configured

Expected results:
Configured hostname would have been removed from those resources.

Additional info:

Comment 3 Wenjing Zheng 2020-04-21 06:15:43 UTC

Verified on 4.5.0-0.nightly-2020-04-18-184707, when set image registry to Removed, internal registry info in below resources are removed too:

zhengwenjings-MacBook-Pro:4.5 wzheng$ oc get cm -n openshift-apiserver image-import-ca -o yaml
apiVersion: v1
kind: ConfigMap
metadata:
  creationTimestamp: "2020-04-20T23:25:48Z"
  name: image-import-ca
  namespace: openshift-apiserver
  resourceVersion: "138884"
  selfLink: /api/v1/namespaces/openshift-apiserver/configmaps/image-import-ca
  uid: cf5d6e7a-f598-4ba1-b70f-c981cb26bfae
zhengwenjings-MacBook-Pro:4.5 wzheng$ oc get image.config.openshift.io/cluster -o yaml
apiVersion: config.openshift.io/v1
kind: Image
metadata:
  annotations:
    release.openshift.io/create-only: "true"
  creationTimestamp: "2020-04-20T23:14:14Z"
  generation: 1
  name: cluster
  resourceVersion: "138456"
  selfLink: /apis/config.openshift.io/v1/images/cluster
  uid: de1cf545-7581-474c-b0be-854b40c2e342
spec: {}
status: {}

Comment 4 errata-xmlrpc 2020-07-13 17:25:52 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:2409