Bug 1747571 - controller-manager pods fail starting after creating trusted-ca-bundle configmap
Summary: controller-manager pods fail starting after creating trusted-ca-bundle configmap
Keywords:
Status: CLOSED DUPLICATE of bug 1747400
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Catalog
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2.0
Assignee: Jesus M. Rodriguez
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-30 20:37 UTC by Daneyon Hansen
Modified: 2019-09-06 17:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-06 17:54:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Daneyon Hansen 2019-08-30 20:37:13 UTC
Description of problem:
svcat-controller-manager pods fail to run after creating trusted-ca-bundle configmap.

Version-Release number of selected component (if applicable):
$ oc get clusteroperators service-catalog-controller-manager
NAME                                 VERSION                         AVAILABLE   PROGRESSING   DEGRADED   SINCE
service-catalog-controller-manager   4.2.0-0.okd-2019-08-29-220902   True        True          False      25m

How reproducible:
Always

Steps to Reproduce:
1. Create a cluster with proxy enabled.
2. Create the trusted-ca configmap


Actual results:
$ oc get all -n openshift-service-catalog-controller-manager


NAME                           READY   STATUS    RESTARTS   AGE
pod/controller-manager-58gx5   0/1     Running   0          5s
pod/controller-manager-cx4dp   1/1     Running   0          15m
pod/controller-manager-nrq4w   1/1     Running   0          15m

NAME                         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)   AGE
service/controller-manager   ClusterIP   172.30.181.251   <none>        443/TCP   15m

NAME                                DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR                     AGE
daemonset.apps/controller-manager   3         3         2       1            2           node-role.kubernetes.io/master=   15m

Expected results:
All pods running.

Additional info:
$ oc logs controller-manager-58gx5 -n openshift-service-catalog-controller-manager -f
W0830 20:21:41.734493       1 feature_gate.go:198] Setting GA feature gate OriginatingIdentity=true. It will be removed in a future release.
I0830 20:21:41.734594       1 hyperkube.go:192] Service Catalog version v4.1.0-0.1.42+7d8b2a2-3-dirty;Upstream:v0.1.42 (built 2019-05-17T13:59:18Z)
I0830 20:21:41.737535       1 leaderelection.go:205] attempting to acquire leader lease

Comment 1 Jesus M. Rodriguez 2019-09-06 17:53:28 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

Comment 2 Jesus M. Rodriguez 2019-09-06 17:54:22 UTC
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 ***


Note You need to log in before you can comment on or make changes to this bug.