Bug 1736843
| Summary: | openshift-service-catalog-apiserver-operator pod is using alpha api | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Liang Xia <lxia> |
| Component: | Service Catalog | Assignee: | Jesus M. Rodriguez <jesusr> |
| Status: | CLOSED ERRATA | QA Contact: | Jian Zhang <jiazha> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.2.0 | CC: | bandrade, chuo, jfan, jiazha, 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-10-16 06:34:29 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: | |||
Liang,
Thanks for your report. But, the `apiVersion` of the `ServiceCatalogAPIServer` resource does `v1`, see below:
mac:~ jianzhang$ oc get servicecatalogapiserver cluster -o yaml
apiVersion: operator.openshift.io/v1
kind: ServiceCatalogAPIServer
metadata:
annotations:
release.openshift.io/create-only: "true"
creationTimestamp: "2019-08-01T01:45:14Z"
generation: 1
name: cluster
resourceVersion: "7402"
selfLink: /apis/operator.openshift.io/v1/servicecatalogapiservers/cluster
uid: 01e76ab8-b3fe-11e9-bb01-02c0576697c8
spec:
logLevel: Normal
managementState: Removed
status:
conditions:
- lastTransitionTime: "2019-08-01T01:49:54Z"
message: the apiserver is in the desired state (Removed).
reason: Removed
status: "True"
type: Available
- lastTransitionTime: "2019-08-01T01:49:54Z"
reason: Removed
status: "False"
type: Progressing
- lastTransitionTime: "2019-08-01T01:49:54Z"
reason: Removed
status: "False"
type: Degraded
readyReplicas: 0
I know your concerns, but the `operator.openshift.io` resource not managged by the ServiceCatalog Operator.
mac:~ jianzhang$ oc get pods
NAME READY STATUS RESTARTS AGE
openshift-service-catalog-apiserver-operator-54f5fc96f9-dn4dt 1/1 Running 0 30h
mac:~ jianzhang$ oc rsh openshift-service-catalog-apiserver-operator-54f5fc96f9-dn4dt
sh-4.2# find . -name config.yaml
./run/configmaps/config/..2019_08_01_01_49_46.183034703/config.yaml
./run/configmaps/config/config.yaml
sh-4.2# cat ./run/configmaps/config/config.yaml
apiVersion: operator.openshift.io/v1alpha1
kind: GenericOperatorConfig
sh-4.2# cat ./run/configmaps/config/..2019_08_01_01_49_46.183034703/config.yaml
apiVersion: operator.openshift.io/v1alpha1
kind: GenericOperatorConfig
sh-4.2# exit
I guess this `operator.openshift.io` group resource is generated by the cvo. Move on it to the Installer team first, please feel free to transfer it to the correct component. Thanks! *** Bug 1736846 has been marked as a duplicate of this bug. *** Definitely, this is a bug from service-catalog https://github.com/openshift/cluster-svcat-apiserver-operator/blob/master/manifests/03_configmap.yaml As @sttts reply in https://coreos.slack.com/archives/CB48XQ4KZ/p1565667523433300 that change was a mistake without consequences. That type is internal only (stored in a configmap not touchable by the user). And we read it without caring about the api version. That's why it did not break. So for now, both of the `v1alpha1` and `v1` are OK. Will change the version to `v1` from `v1alpha1` on 4.3. https://github.com/openshift/api/blob/master/operator/v1alpha1/register.go#L11-L12 Anyway, verify this bug first. Cluster version is 4.2.0-0.nightly-2019-08-08-103722 version info: io.openshift.build.commit.url=https://github.com/openshift/cluster-svcat-apiserver-operator/commit/926d8cbf2a4710d4aba6a286b3ee0880b3fe9762 io.openshift.build.source-location=https://github.com/openshift/cluster-svcat-apiserver-operator mac:~ jianzhang$ oc get pods NAME READY STATUS RESTARTS AGE openshift-service-catalog-apiserver-operator-6f99f6bbfc-zfrnp 1/1 Running 0 5h23m mac:~ jianzhang$ oc rsh openshift-service-catalog-apiserver-operator-6f99f6bbfc-zfrnp sh-4.2# service-catalog --version sh: service-catalog: command not found sh-4.2# sh-4.2# find . -name config.yaml ./run/configmaps/config/..2019_08_13_03_19_13.063664956/config.yaml ./run/configmaps/config/config.yaml sh-4.2# cat ./run/configmaps/config/config.yaml apiVersion: operator.openshift.io/v1 kind: GenericOperatorConfig sh-4.2# cat ./run/configmaps/config/..2019_08_13_03_19_13.063664956/config.yaml apiVersion: operator.openshift.io/v1 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:2922 |
Description of problem: openshift-service-catalog-apiserver-operator pod is using alpha api Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-07-28-222114 Client Version: version.Info{Major:"4", Minor:"2+", GitVersion:"v4.2.0", GitCommit:"1cca013db", GitTreeState:"clean", BuildDate:"2019-08-01T18:56:59Z", GoVersion:"go1.12.6", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.0+1682e38", GitCommit:"1682e38", GitTreeState:"clean", BuildDate:"2019-07-28T20:08:40Z", GoVersion:"go1.12.6", Compiler:"gc", Platform:"linux/amd64"} OpenShift Version: 4.2.0-0.nightly-2019-07-28-222114 How reproducible: Always Steps to Reproduce: 1.oc project openshift-service-catalog-apiserver-operator 2.oc get pods 3.oc rsh $above_pod 4.find . -name config.yaml -exec cat {} \; Actual results: apiVersion: operator.openshift.io/v1alpha1 kind: GenericOperatorConfig Expected results: alpha api should not be used for prod cluster. Additional info: