Bug 1467307
Summary: | catalog controller manager pod is not running with openshift v3.6.131 | ||||||
---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Johnny Liu <jialiu> | ||||
Component: | Node | Assignee: | Jeff Peeler <jpeeler> | ||||
Status: | CLOSED ERRATA | QA Contact: | Johnny Liu <jialiu> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 3.6.0 | CC: | aos-bugs, deads, decarr, dma, eparis, jokerman, jpeeler, mmccomas, sdodson | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
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: | 2017-08-10 05:29:50 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: | |||||||
Attachments: |
|
Description
Johnny Liu
2017-07-03 11:03:56 UTC
kubectl api-versions is not returning servicecatalog.k8s.io/v1alpha1 as expected, but I don't know why discovery is not finding that group. The problem doesn't appear to be with the certificates or with the discovery cache being stale. We tried again in https://github.com/openshift/origin/pull/15022. I'm surprised it took this long to fail. These tests don't block merge? Jeff to verify with latest commit, on success move to MODIFIED. origin/master is working as expected Verified this bug with openshift3/ose-service-catalog:latest (eb2a9b361302) and atomic-openshift-3.6.135-1.git.0.56fd7dc.el7.x86_64, installation is finished successfully, and controller-manager is running well. # oc get po NAME READY STATUS RESTARTS AGE apiserver-462z1 1/1 Running 0 5h controller-manager-hdpgj 1/1 Running 1 5h 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, 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/RHEA-2017:1716 |