Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1724484

Summary: openshift-apiserver-operator pod is using alpha api
Product: OpenShift Container Platform Reporter: Liang Xia <lxia>
Component: openshift-apiserverAssignee: Michal Fojtik <mfojtik>
Status: CLOSED ERRATA QA Contact: Xingxing Xia <xxia>
Severity: high Docs Contact:
Priority: high    
Version: 4.2.0CC: aos-bugs, ccoleman, deads, jiazha, mfojtik, sttts
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:32:41 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 Liang Xia 2019-06-27 07:41:14 UTC
Description of problem:
openshift-apiserver-operator pod is using alpha api


Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-06-26-211837
Client Version: version.Info{Major:"4", Minor:"2+", GitVersion:"v4.2.0", GitCommit:"250bfaa6f", GitTreeState:"clean", BuildDate:"2019-06-27T02:28:53Z", GoVersion:"go1.12.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.0+e965019", GitCommit:"e965019", GitTreeState:"clean", BuildDate:"2019-06-26T19:18:36Z", GoVersion:"go1.12.6", Compiler:"gc", Platform:"linux/amd64"}

How reproducible:
Always

Steps to Reproduce:
1.oc project openshift-apiserver-operator
2.oc get pods
3.oc rsh openshift-apiserver-operator-799f898665-wgc2r
4.ps -q 1 -o cmd
5.cat /var/run/configmaps/config/config.yaml

Actual results:
sh-4.2# cat /var//run/configmaps/config/config.yaml 
apiVersion: operator.openshift.io/v1alpha1
kind: GenericOperatorConfig


Expected results:
alpha api should not be used for prod cluster.

Additional info:

Comment 3 Liang Xia 2019-08-02 03:54:17 UTC
Verified the issue has been fixed on 4.2.0-0.nightly-2019-07-28-222114

$ oc project openshift-apiserver-operator 
Now using project "openshift-apiserver-operator" on server "https://qe-test-server:6443".

$ oc get pods
NAME                                           READY   STATUS    RESTARTS   AGE
openshift-apiserver-operator-f9bcf88b4-5lhp8   1/1     Running   1          4d1h

$ oc rsh openshift-apiserver-operator-f9bcf88b4-5lhp8 
sh-4.2# cat /var/run/configmaps/config/config.yaml 
apiVersion: operator.openshift.io/v1
kind: GenericOperatorConfig

Comment 4 Jian Zhang 2019-08-03 05:13:53 UTC
Hi, Michal, Stefan

I couldn't find this kind in the cluster, and the `oc explain` doesn't help either. Could you help explain more about this `GenericOperatorConfig` resource?
And, what this ConfigMap does here? Thanks!
mac:~ jianzhang$ oc get GenericOperatorConfig
error: the server doesn't have a resource type "GenericOperatorConfig"

Comment 5 Jian Zhang 2019-08-06 07:44:04 UTC
+ David

Could you help answer my concerns in comment 4? Thanks!
And, I find the definition of `GenericOperatorConfig` in https://github.com/openshift/api/blob/master/operator/v1alpha1/types.go#L127.
But, the version still is `v1alpha1`, why? Or am I missing something?

Comment 6 Jian Zhang 2019-08-12 06:48:40 UTC
+ Clayton

Could you help address my concerns in comment 4, 5? Thanks! Or am I missing something?

Comment 7 David Eads 2019-08-12 13:42:11 UTC
It is a serialized-only file that doesn't have an api representation and that we do not support direct user action for.  Because of that, we don't expect to display a GenericOperatorConfig type.  We can ship with the serialization listed incorrectly (we force it to be consumeable in the code).  

@sttts probably want to promote the type to v1.

Comment 8 Jian Zhang 2019-08-13 03:29:04 UTC
Hi, David

Many thanks for your explanation! 

> probably want to promote the type to v1.

So, we should also change https://github.com/openshift/api/blob/master/operator/v1alpha1/types.go#L127 version to `v1`, right?
I'm confused, for this bug, only fixed the version in /var/run/configmaps/config/config.yaml (change version to `v1` from the `v1alpha1`).
But, the version in https://github.com/openshift/api/blob/master/operator/v1alpha1/types.go#L127 still is `v1alpha1`, so how does this ConfigMap work?

Comment 10 errata-xmlrpc 2019-10-16 06:32:41 UTC
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

Comment 11 Red Hat Bugzilla 2023-09-14 05:30:58 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days