-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.14
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
Yes
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Observed pods exist in openshift-console namespace in spoke cluster after installing spoke cluster with 4.14 nightly build
Version-Release number of selected component (if applicable):
4.14.0-0.nightly-2023-08-11-055332
How reproducible:
100%
Steps to Reproduce:
Deploy Spoke/Managed Cluster using GitOps ZTP pipeline Export Spoke Cluster kubeconfig file and check the Spoke Cluster is UP and running. Verify pods do not exist in openshift-console namespace using below command $ "oc get pods -n openshift-console"
Actual results:
pod exist in openshift-console namespace
Expected results:
pods should not exist in openshift-console namespace. In other words, No resources found in openshift-console namespace is expected on spoke cluster.
Additional info:
[kni@registry.kni-qe-53 ~]$ kni-login [kni@registry.kni-qe-53 ~]$ [kni@registry.kni-qe-53 ~]$ [kni@registry.kni-qe-53 ~]$ oc get managedcluster NAME HUB ACCEPTED MANAGED CLUSTER URLS JOINED AVAILABLE AGE helix56 true https://api.helix56.lab.eng.rdu2.redhat.com:6443 True True 17h local-cluster true https://api.kni-qe-53.telco5gran.eng.rdu2.redhat.com:6443 True True 3d13h [kni@registry.kni-qe-53 ~]$ [kni@registry.kni-qe-53 ~]$ export KUBECONFIG=/home/kni/clusterconfigs/helix56/auth/kubeconfig [kni@registry.kni-qe-53 ~]$ oc get po -n openshift-console NAME READY STATUS RESTARTS AGE console-74bbddc8f5-26kgm 1/1 Running 0 16h downloads-78479fb8cf-gxc4j 1/1 Running 0 16h [kni@registry.kni-qe-53 ~]$ oc version Client Version: 4.14.0-0.nightly-2023-08-11-055332 Kustomize Version: v5.0.1 Server Version: 4.14.0-0.nightly-2023-08-11-055332 Kubernetes Version: v1.27.4+deb2c60 [kni@registry.kni-qe-53 ~]$