Red Hat Bugzilla – Bug 1583093
Unused registry-console's ImageStream is deployed
Last modified: 2018-06-27 03:59:49 EDT
Description of problem: - Unused registry-console's ImageStream is deployed. Version-Release number of the following components: # rpm -q openshift-ansible openshift-ansible-3.9.14-1.git.3.c62bc34.el7.noarch # rpm -q ansible ansible-2.4.3.0-1.el7ae.noarch How reproducible: 100% Steps to Reproduce: 1. Install OCP 3.9 Actual results: - ImageStream of registry-console is deployed "# oc get is -n default registry-console". - However, DC refers image in registry.redhat.com # oc get dc -n default registry-console -o yaml |grep image: image: openshift3/registry-console:v3.9 Expected results: - ImageStream is not deployed, if it is not referred from anywhere. Additional info: - Proposed patch: https://github.com/openshift/openshift-ansible/pull/8545
1. The PR is targeted to 3.10, but this bug's "Target Release" is 3.7, is that true? 2. Even this bug's target release should be corrected to 3.10, the PR is already reverted, because it is causing new issue - BZ#1584966.
New PR to remove imagestream - https://github.com/openshift/openshift-ansible/pull/8545, merged in openshift-ansible-3.10.0-0.65.0
Just as what I said in comment 2, the PR#8545 is already reverted because it is causing BZ#1584966. Based on the the above discuss, I think this bug should be targeted for v3.10, so move target release to 3.10.z.
Oops, wrong PR link. Correct PR is https://github.com/openshift/openshift-ansible/pull/8621
Fix is available in openshift-ansible-3.10.0-0.66.0
Verified this bug with openshift-ansible-3.10.0-0.67.0.git.107.1bd1f01.el7.noarch, and PASS. No registry-console imagestream is created. [root@qe-jialiu3102-master-etcd-1 ~]# oc get po NAME READY STATUS RESTARTS AGE docker-registry-1-s2n6k 1/1 Running 0 3h registry-console-1-b5n5w 1/1 Running 0 3h router-1-9lqls 1/1 Running 0 3h [root@qe-jialiu3102-master-etcd-1 ~]# oc get is No resources found.
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-2018:2009