Bug 1851874
Summary: | In-tree provisioner doesn't work on GCP | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Wei Duan <wduan> |
Component: | kube-controller-manager | Assignee: | Tomáš Nožička <tnozicka> |
Status: | CLOSED ERRATA | QA Contact: | zhou ying <yinzhou> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.5 | CC: | aos-bugs, jsafrane, maszulik, mfojtik |
Target Milestone: | --- | ||
Target Release: | 4.6.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-10-27 16:09:46 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Wei Duan
2020-06-29 09:59:25 UTC
The reason is that kube-controller-manager is degraded: $ oc get clusteroperator kube-controller-manager -o yaml - lastTransitionTime: "2020-06-29T08:15:44Z" message: "ConfigObservationDegraded: .spec.featureSet %!q(*v1.FeatureGateEnabledDisabled=<nil>) not found\nStaticPodsDegraded: pod/kube-controller-manager-yinzhougcp-k2fqv-master-1.c.openshift-qe.internal container \"cluster-policy-controller\" is not ready: unknown reason\nStaticPodsDegraded: pod/kube-controller-manager-yinzhougcp-k2fqv-master-1.c.openshift-qe.internal container \"cluster-policy-controller\" is terminated: Error: I0629 11:22:13.896668 \ 1 policy_controller.go:41] Starting controllers on 0.0.0.0:10357 (d88621be)\nStaticPodsDegraded: I0629 11:22:13.898539 1 standalone_apiserver.go:103] Started health checks at 0.0.0.0:10357\nStaticPodsDegraded: I0629 11:22:13.899177 1 leaderelection.go:242] attempting to acquire leader lease openshift-kube-controller-manager/cluster-policy-controller...\nStaticPodsDegraded: F0629 11:22:13.899898 1 standalone_apiserver.go:119] listen tcp 0.0.0.0:10357: bind: address already in use\nStaticPodsDegraded: \nStaticPodsDegraded: pod/kube-controller-manager-yinzhougcp-k2fqv-master-1.c.openshift-qe.internal container \"kube-controller-manager\" is not ready: unknown reason" reason: ConfigObservation_Error::StaticPods_Error status: "True" type: Degraded After deleting the kube-controller-manager pods (not the operator), I got this from kube-controller-manager: - lastTransitionTime: "2020-06-29T08:15:44Z" message: 'ConfigObservationDegraded: .spec.featureSet %!q(*v1.FeatureGateEnabledDisabled=<nil>) not found' reason: ConfigObservation_Error status: "True" type: Degraded Can you either provide us with a cluster where this is happening or must-gather dump from that cluster? I'm especially interested in the following resources: oc get featuregates/cluster -oyaml oc get kubecontrollermanager/cluster -oyaml Sorry I missed the "needinfo" notify and the cluster was removed already. I set up a new cluster with the same flexy template and the 4.5.0-0.nightly-2020-07-02-190154 last friday, I did not hit this issue again. I'm lowering the priority based on previous comment, when you hit the issue again please let us know. I removed the TestBlocker tag. It looks like this might have been fixed with https://github.com/openshift/cluster-kube-controller-manager-operator/pull/415 moving to qa for verification. Confirmed with payload: 4.6.0-0.nightly-2020-07-07-141639 [root@dhcp-140-138 ~]# oc get po NAME READY STATUS RESTARTS AGE mypod 0/1 ErrImagePull 0 4m24s [zhouying@dhcp-140-138 ~]$ oc get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE ebs Bound pvc-f439d62c-3611-49cb-8cc8-ca4931998394 1Gi RWO standard 49s 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 (OpenShift Container Platform 4.6 GA Images), 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-2020:4196 |