-
Bug
-
Resolution: Duplicate
-
Critical
-
None
-
4.14.z, 4.15.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
No
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Some operators are not ready for HCP cluster that is set Other Network type
Version-Release number of selected component (if applicable):
4.14.z and 4.15-candiate
How reproducible:
always
Steps to Reproduce:
1.Create a HCP cluster with '--no-cni' to use Other network type
2.After cluster ready and login it to install cilium
$ oc create ns cilium
$ oc label ns cilium security.openshift.io/scc.podSecurityLabelSync=false
$ oc label ns cilium pod-security.kubernetes.io/enforce=privileged --overwrite
$ oc label ns cilium pod-security.kubernetes.io/audit=privileged --overwrite $oc label ns cilium pod-security.kubernetes.io/warn=privileged --overwrite
# clone cilium-olm to local env and install it as operators
git clone git@github.com:cilium/cilium-olm.git
cd $GOPATH/src/github.com/cilium/cilium-olm/manifests/cilium.v1.13.0/
$ oc apply -f .
$ oc apply -f .
3.Wait for nodepool / operator ready
Actual results:
1. nodepools are ready after installing cilium
2. Operators are not ready
oc get co -A
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console
csi-snapshot-controller 4.15.0-rc.3 True False False 3h40m
dns 4.15.0-rc.3 False True True 3h40m DNS "default" is unavailable.
image-registry False True True 3h39m Available: The deployment does not have available replicas...
ingress False True True 3h40m The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights
kube-apiserver 4.15.0-rc.3 True False False 3h40m
kube-controller-manager 4.15.0-rc.3 True False False 3h40m
kube-scheduler 4.15.0-rc.3 True False False 3h40m
kube-storage-version-migrator
monitoring
network 4.15.0-rc.3 True True False 3h40m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes)...
node-tuning 4.15.0-rc.3 True False False 11m
openshift-apiserver 4.15.0-rc.3 True False False 3h40m
openshift-controller-manager 4.15.0-rc.3 True False False 3h40m
openshift-samples
operator-lifecycle-manager 4.15.0-rc.3 True False False 3h40m
operator-lifecycle-manager-catalog 4.15.0-rc.3 True False False 3h40m
operator-lifecycle-manager-packageserver 4.15.0-rc.3 True False False 3h40m
service-ca
storage 4.15.0-rc.3 True False False 11m
Expected results:
Operators should be ready in HCP cluster
Additional info:
Some operator/pod debug log
https://privatebin.corp.redhat.com/?c6986a270f53a3ab#Efxc4ucfLGcknnUxhhdQxXsNBrzWuza6Bhj8qCFZ78ub