-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.19
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
HCP pods are not coming properly from 4.19.0-rc.2-multi
Version-Release number of selected component (if applicable):
4.19.0-rc.2,3
How reproducible:
always
Steps to Reproduce:
1. Create an x86 or s390x OCP cluster ( hub cluster )
2. Install MCE 2.9
3.Create a hosted Control Plane with version 4.19.0-rc.2 or rc.3 multi.
Actual results:
[root@m42lp51 ~]# oc get po -n hcp-dpm-ns-hcp-dpm NAME READY STATUS RESTARTS AGE capi-provider-5f6d5b659c-m8dkf 1/1 Running 0 18m cluster-api-8c9c69b75-mrz7v 1/1 Running 0 18m cluster-network-operator-67db9d88c8-x5pnt 3/3 Running 0 15m cluster-node-tuning-operator-7b56dc8d65-pvqbq 1/1 Running 0 15m cluster-policy-controller-58d5bd48fb-qkhv9 1/1 Running 0 16m control-plane-operator-7f8b4c89f7-2zbs8 1/1 Running 0 18m control-plane-pki-operator-794465cfd5-x9vpr 1/1 Running 0 17m dns-operator-54f79b4c5f-6wnkp 1/1 Running 0 15m etcd-0 3/3 Running 0 17m featuregate-generator-sszpp 0/1 Completed 0 16m hosted-cluster-config-operator-7b69cff697-kv855 1/1 Running 0 15m ignition-server-67b857459b-8dtdt 1/1 Running 0 16m ignition-server-proxy-64f44b9ccd-bzwqz 1/1 Running 0 16m ingress-operator-587fd4d59b-sddtz 2/2 Running 0 15m konnectivity-agent-595dd65b6-d5g7m 1/1 Running 0 16m kube-apiserver-758b9cdd77-vj5xt 4/4 Running 0 16m kube-controller-manager-68cc794b77-9r86b 1/1 Running 0 14m kube-scheduler-6bcffb9cd4-9jch8 1/1 Running 0 16m oauth-openshift-7d47f46b5f-k46z8 4/4 Running 0 15m openshift-apiserver-6bc9fb995b-66hdv 3/3 Running 0 16m openshift-controller-manager-784cdc4467-k5cts 1/1 Running 0 16m openshift-oauth-apiserver-65c897b644-dtdv7 3/3 Running 0 16m openshift-route-controller-manager-5c95b468b-c2pjv 1/1 Running 0 16m
Expected results:
[root@hcp-dpm-bastion ~]# oc get po -n hcp-dpm-ns-hcp-dpm NAME READY STATUS RESTARTS AGE capi-provider-5564765c98-rlhtl 1/1 Running 0 8m43s catalog-operator-745d5c8d7b-k56j7 2/2 Running 0 5m15s certified-operators-catalog-75b79f7f4-t5w65 1/1 Running 0 4m58s cluster-api-594b54cfcf-xpgvj 1/1 Running 0 8m46s cluster-image-registry-operator-6dcd4f65bd-hhv58 2/2 Running 0 5m14s cluster-network-operator-5c7748d7b5-9mchf 3/3 Running 0 5m24s cluster-node-tuning-operator-6fbcc46cf5-nx2bl 1/1 Running 0 5m23s cluster-policy-controller-6f479b8bd4-6z2gp 1/1 Running 0 5m25s cluster-storage-operator-7c6bb77f5-xhgf2 1/1 Running 0 5m14s cluster-version-operator-75dcddcb84-7rbc8 1/1 Running 0 5m24s community-operators-catalog-59c65cdb5d-cpnnm 1/1 Running 0 4m58s control-plane-operator-844d6bd445-r65w8 1/1 Running 0 8m41s control-plane-pki-operator-69b4dfffc9-26qzr 1/1 Running 0 6m45s csi-snapshot-controller-fc6bb6d8-qb4df 1/1 Running 0 47s csi-snapshot-controller-operator-6499c6b889-7vxzv 1/1 Running 0 5m14s dns-operator-66f5977955-hsbz2 1/1 Running 0 5m22s etcd-0 3/3 Running 0 6m45s hosted-cluster-config-operator-7f8b9b74d-cwbn7 1/1 Running 0 5m20s ignition-server-d58f58c9f-dzk2m 1/1 Running 0 5m26s ignition-server-proxy-7f4666bcd4-kd44t 1/1 Running 0 5m26s ingress-operator-9494b77f4-ns9bs 2/2 Running 0 5m21s konnectivity-agent-dc7b75bdb-qtvlv 1/1 Running 0 5m26s kube-apiserver-659bcc84f7-wnkzs 4/4 Running 0 6m21s kube-controller-manager-74778bcb84-f5trz 1/1 Running 0 42s kube-scheduler-6f79d98c8b-f2pr4 1/1 Running 0 6m9s machine-approver-5976f5fb99-xc8vf 1/1 Running 0 5m13s oauth-openshift-7db64b8cf7-gz6lj 4/4 Running 0 60s olm-operator-ff65fc7c8-4cbbf 2/2 Running 0 5m15s openshift-apiserver-6845c799c7-mttm8 3/3 Running 0 6m9s openshift-controller-manager-89fbc894d-7qmkq 1/1 Running 0 5m26s openshift-oauth-apiserver-6f6ddfc7bd-9mc49 3/3 Running 0 5m26s openshift-route-controller-manager-56799b79d4-rmctd 1/1 Running 0 5m26s packageserver-5b9b7544cd-pdk7r 2/2 Running 0 5m15s redhat-marketplace-catalog-56bd5dd577-p65zh 1/1 Running 0 4m58s redhat-operators-catalog-bcd75c996-dxwhs 1/1 Running 0 4m58s
Additional info:
