Bug 1747571
Summary: | controller-manager pods fail starting after creating trusted-ca-bundle configmap | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Daneyon Hansen <dhansen> |
Component: | Service Catalog | Assignee: | Jesus M. Rodriguez <jesusr> |
Status: | CLOSED DUPLICATE | QA Contact: | Jian Zhang <jiazha> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.2.0 | CC: | bandrade, chuo, jfan, scolange |
Target Milestone: | --- | ||
Target Release: | 4.2.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-09-06 17:54:22 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
Daneyon Hansen
2019-08-30 20:37:13 UTC
$ oc get clusteroperators service-catalog-controller-manager NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE service-catalog-controller-manager 4.2.0-0.nightly-2019-09-04-142146 True False False 2m59s $ oc get all -n openshift-service-catalog-controller-manager NAME READY STATUS RESTARTS AGE pod/controller-manager-294lt 1/1 Running 0 4m pod/controller-manager-5x89z 1/1 Running 0 4m pod/controller-manager-fklbh 1/1 Running 0 4m NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/controller-manager ClusterIP 172.30.85.168 <none> 443/TCP 4m24s NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE daemonset.apps/controller-manager 3 3 3 3 3 node-role.kubernetes.io/master= 4m24s $ oc get apiservice v1beta1.servicecatalog.k8s.io NAME SERVICE AVAILABLE AGE v1beta1.servicecatalog.k8s.io openshift-service-catalog-apiserver/api True 6m16s While fixing Bug 1747400 it fixes this bug. I'm marking this bug a duplicate of 1747400. *** This bug has been marked as a duplicate of bug 1747400 *** |