Description of problem: During deploy cns as docker registry back end storage, cns pods should be in same namespace(default) as docker-registry. Version-Release number of the following components: openshift-ansible-3.6.173.0.103-1.git.0.dcf417c.el7 How reproducible: 100% Steps to Reproduce: 1. Deploy CNS as docker registry back end storage 2. 3. Actual results: # oc get po -n default NAME READY STATUS RESTARTS AGE docker-registry-1-45l82 1/1 Running 0 2h registry-console-1-m2fr7 1/1 Running 0 2h router-1-njvrn 1/1 Running 0 2h # oc get po -n glusterfs NAME READY STATUS RESTARTS AGE glusterblock-registry-provisioner-dc-1-b6326 1/1 Running 0 2h glusterfs-registry-r0wr3 1/1 Running 0 2h glusterfs-registry-s0h60 1/1 Running 0 2h glusterfs-registry-vc16c 1/1 Running 0 2h heketi-registry-1-0k1vb 1/1 Running 0 2h Expected results: CNS related pods should in default namespace in this case. Additional info:
Change target release to 3.6.z since 3.9 doesn't has such issue.
Please check to see if the issue is still present after the various fixes since this has been raised.
(In reply to Jose A. Rivera from comment #2) > Please check to see if the issue is still present after the various fixes > since this has been raised. Check with version openshift-ansible-3.6.173.0.124-1.git.0.5f3f028.el7, this issue still appear. # oc get po NAME READY STATUS RESTARTS AGE docker-registry-1-6c2zx 1/1 Running 0 5m registry-console-1-9hvsh 1/1 Running 0 3m router-1-nqqd2 1/1 Running 0 6m # oc get po -n glusterfs NAME READY STATUS RESTARTS AGE glusterblock-registry-provisioner-dc-1-3p4jn 1/1 Running 0 8m glusterfs-registry-6t78v 1/1 Running 0 13m glusterfs-registry-dqcx9 1/1 Running 0 13m glusterfs-registry-h4f06 1/1 Running 0 13m heketi-registry-1-r0z13 1/1 Running 0 9m # oc version oc v3.6.173.0.124 kubernetes v1.6.1+5115d708d7 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://qe-weshi-cns36-master-1:8443 openshift v3.6.173.0.124 kubernetes v1.6.1+5115d708d7
Failed to verify with version openshift-ansible-3.6.173.0.126-1.git.0.47264f0.el7, this issue still appear. # oc get po -n default NAME READY STATUS RESTARTS AGE docker-registry-1-x1k6b 1/1 Running 0 3h registry-console-1-v6cxj 1/1 Running 0 3h router-1-bskb4 1/1 Running 0 3h # oc get po -n glusterfs NAME READY STATUS RESTARTS AGE glusterblock-registry-provisioner-dc-1-32vt1 1/1 Running 0 3h glusterfs-registry-2wc9r 1/1 Running 0 3h glusterfs-registry-74pjz 1/1 Running 0 3h glusterfs-registry-9kqhl 1/1 Running 0 3h heketi-registry-1-p2wkp 1/1 Running 0 3h # oc version oc v3.6.173.0.126 kubernetes v1.6.1+5115d708d7 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://qe-weshi-36cnsr-master-1:8443 openshift v3.6.173.0.126 kubernetes v1.6.1+5115d708d7
Have you taken a look at the failure?
I believe this is no longer relevant since 3.6 should be out of support.
(In reply to Jose A. Rivera from comment #8) > I believe this is no longer relevant since 3.6 should be out of support. And it's irrelevant for other releases? So please close it.
Right-o. :)