Bug 1688132
| Summary: | Missing version info for cluster operator service-ca | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Liang Xia <lxia> |
| Component: | apiserver-auth | Assignee: | Erica von Buelow <evb> |
| Status: | CLOSED ERRATA | QA Contact: | Chuan Yu <chuyu> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.1.0 | CC: | aos-bugs, jiazha, jokerman, mmccomas, spadgett, yufchang |
| Target Milestone: | --- | ||
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1688122 | Environment: | |
| Last Closed: | 2019-06-04 10:45:47 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1688122 | ||
| Bug Blocks: | 1688131 | ||
|
Description
Liang Xia
2019-03-13 08:33:09 UTC
Fixed in service catalog controller manager via https://github.com/openshift/cluster-svcat-controller-manager-operator/pull/25 and should be in builds 4.0.0-0.alpha-2019-03-14 and newer. *pending* in service catalog apiserver via https://github.com/openshift/cluster-svcat-apiserver-operator/pull/39 both prs have merged. $ oc get clusteroperators | grep service service-ca True False False 27m service-catalog-apiserver 4.0.0-0.alpha-2019-03-14-014544 True False False 23m service-catalog-controller-manager 4.0.0-0.alpha-2019-03-14-014544 True False False 23m The issue for service-catalog-apiserver/service-catalog-controller-manager are fixed. @Jay, Are your team responsible for the operator service-ca ? If not, i can verify this bug and open a new one to track that. Service Catalog operators works well, moving this bug to Auth team since the "service-ca" has not been fixed yet. [jzhang@dhcp-140-18 ocp14]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-03-13-233958 True False 117m Cluster version is 4.0.0-0.nightly-2019-03-13-233958 [jzhang@dhcp-140-18 ocp14]$ oc get clusteroperator NAME VERSION AVAILABLE PROGRESSING FAILING SINCE cluster-autoscaler 4.0.0-0.nightly-2019-03-13-233958 True False False 124m console 4.0.0-0.nightly-2019-03-13-233958 True False False 114m dns 4.0.0-0.nightly-2019-03-13-233958 True False False 123m image-registry 4.0.0-0.nightly-2019-03-13-233958 True False False 118m ingress 4.0.0-0.nightly-2019-03-13-233958 True False False 118m kube-apiserver 4.0.0-0.nightly-2019-03-13-233958 True False False 121m kube-controller-manager 4.0.0-0.nightly-2019-03-13-233958 True False False 122m kube-scheduler 4.0.0-0.nightly-2019-03-13-233958 True False False 123m machine-api 4.0.0-0.nightly-2019-03-13-233958 True False False 124m machine-config 4.0.0-0.nightly-2019-03-13-233958 True False False 124m marketplace-operator 4.0.0-0.nightly-2019-03-13-233958 True False False 118m monitoring 4.0.0-0.nightly-2019-03-13-233958 True False False 2m46s network 4.0.0-0.nightly-2019-03-13-233958 True False False 118m node-tuning 4.0.0-0.nightly-2019-03-13-233958 True False False 118m openshift-apiserver 4.0.0-0.nightly-2019-03-13-233958 True False False 119m openshift-authentication True False False 118m openshift-cloud-credential-operator True False False 124m openshift-controller-manager 4.0.0-0.nightly-2019-03-13-233958 True False False 119m openshift-samples 4.0.0-0.nightly-2019-03-13-233958 True False False 117m operator-lifecycle-manager 0.8.1-31e16a9 True False False 124m service-ca True False False 124m service-catalog-apiserver 4.0.0-0.nightly-2019-03-13-233958 True False False 118m service-catalog-controller-manager 4.0.0-0.nightly-2019-03-13-233958 True False False 118m storage 4.0.0-0.nightly-2019-03-13-233958 True False False 118m $ oc get clusteroperators NAME VERSION AVAILABLE PROGRESSING FAILING SINCE authentication 4.0.0-0.alpha-2019-03-18-221255 True False False 7m25s cluster-autoscaler 4.0.0-0.alpha-2019-03-18-221255 True False False 13m console 4.0.0-0.alpha-2019-03-18-221255 True False False 2m40s dns 4.0.0-0.alpha-2019-03-18-221255 True False False 12m image-registry 4.0.0-0.alpha-2019-03-18-221255 True False False 7m ingress 4.0.0-0.alpha-2019-03-18-221255 True False False 7m1s kube-apiserver 4.0.0-0.alpha-2019-03-18-221255 True False False 9m kube-controller-manager 4.0.0-0.alpha-2019-03-18-221255 True False False 10m kube-scheduler 4.0.0-0.alpha-2019-03-18-221255 True False False 11m machine-api 4.0.0-0.alpha-2019-03-18-221255 True False False 13m machine-config 4.0.0-0.alpha-2019-03-18-221255 True False False 12m marketplace-operator 4.0.0-0.alpha-2019-03-18-221255 True False False 7m15s monitoring 4.0.0-0.alpha-2019-03-18-221255 True False False 105s network 4.0.0-0.alpha-2019-03-18-221255 True False False 13m node-tuning 4.0.0-0.alpha-2019-03-18-221255 True False False 7m27s openshift-apiserver 4.0.0-0.alpha-2019-03-18-221255 True False False 8m20s openshift-cloud-credential-operator 4.0.0-0.alpha-2019-03-18-221255 True False False 12m openshift-controller-manager 4.0.0-0.alpha-2019-03-18-221255 True False False 11m openshift-samples 4.0.0-0.alpha-2019-03-18-221255 True False False 6m22s operator-lifecycle-manager 4.0.0-0.alpha-2019-03-18-221255 True False False 13m service-ca True False False 12m service-catalog-apiserver 4.0.0-0.alpha-2019-03-18-221255 True False False 7m29s service-catalog-controller-manager 4.0.0-0.alpha-2019-03-18-221255 True False False 7m32s storage 4.0.0-0.alpha-2019-03-18-221255 True False False 7m34s The last cluster operator which is missing version info The issue should be fixed with https://github.com/openshift/service-ca-operator/pull/34 merged. $ oc get clusteroperator service-ca NAME VERSION AVAILABLE PROGRESSING FAILING SINCE service-ca 4.0.0-0.nightly-2019-03-23-183709 True False False 3h16m Verified. oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-03-23-183709 True True 3h28m 4.0.0-0.nightly-2019-03-23-183709 *** Bug 1679077 has been marked as a duplicate of this bug. *** 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/RHBA-2019:0758 |