Description of problem: Executing oc explain apiservers.spec gets empty DESCRIPTION Version-Release number of selected component (if applicable): $ oc version -o yaml clientVersion: buildDate: "2020-01-03T06:08:27Z" compiler: gc gitCommit: 6a937dfe56ff26255d09702c69b8406040c14505 gitTreeState: clean gitVersion: v4.3.0 goVersion: go1.12.12 major: "" minor: "" platform: linux/amd64 openshiftVersion: 4.3.0-0.nightly-2020-01-07-212456 serverVersion: buildDate: "2020-01-03T07:57:59Z" compiler: gc gitCommit: 956b3a5 gitTreeState: clean gitVersion: v1.16.2 goVersion: go1.12.12 major: "1" minor: 16+ platform: linux/amd64 How reproducible: Always Steps to Reproduce: 1.Executing oc explain apiservers.spec Actual results: $ oc explain apiservers.spec KIND: APIServer VERSION: config.openshift.io/v1 RESOURCE: spec <Object> DESCRIPTION: <empty> ... Expected results: Executing oc explain apiservers.spec The field DESCRIPTION should have the content for apiservers.spec Additional info:
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale". If you have further information on the current state of the bug, please update it, otherwise this bug will be automatically closed in 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Verified with build 4.5.0-0.nightly-2020-05-12-195228, $ oc explain apiservers.spec KIND: APIServer VERSION: config.openshift.io/v1 RESOURCE: spec <Object> DESCRIPTION: <empty> FIELDS: additionalCORSAllowedOrigins <[]string> additionalCORSAllowedOrigins lists additional, user-defined regular expressions describing hosts for which the API server allows access using the CORS headers. This may be needed to access the API and the integrated OAuth server from JavaScript applications. The values are regular expressions that correspond to the Golang regular expression language. clientCA <Object> clientCA references a ConfigMap containing a certificate bundle for the signers that will be recognized for incoming client certificates in addition to the operator managed signers. If this is empty, then only operator managed signers are valid. You usually only have to set this if you have your own PKI you wish to honor client certificates from. The ConfigMap must exist in the openshift-config namespace and contain the following required fields: - ConfigMap.Data["ca-bundle.crt"] - CA bundle. encryption <Object> encryption allows the configuration of encryption of resources at the datastore layer. servingCerts <Object> servingCert is the TLS cert info for serving secure traffic. If not specified, operator managed certificates will be used for serving secure traffic. tlsSecurityProfile <Object> tlsSecurityProfile specifies settings for TLS connections for externally exposed servers. If unset, a default (which may change between releases) is chosen. Note that only Old and Intermediate profiles are currently supported, and the maximum available MinTLSVersions is VersionTLS12.
Missed DESCRIPTION checking, in the latest payload, the problem still existed. See below, DESCRIPTION: <empty> So reopened it.
Checked the latest payload 4.5.0-0.nightly-2020-05-12-195228, the latest merged PR date is on May 9, the PR of this bug has not been included, waiting for next payload. [ke@fedpc openshift-apiserver]$ oc adm release info --commits registry.svc.ci.openshift.org/ocp/release:4.5.0-0.nightly-2020-05-12-195228 | grep openshift-apiserver ... openshift-apiserver https://github.com/openshift/openshift-apiserver 4c982be0e64177b727200e416aa6375f4f17ffc2 [ke@fedpc openshift-apiserver]$ git log --date local --pretty="%h %an %cd - %s" 4c982be0 -1 4c982be0e OpenShift Merge Robot Sat May 9 01:00:16 2020 - Merge pull request #102 from gabemontero/copy-upstream-k8s-k8s-pull-90534
$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.0-0.nightly-2020-05-24-223848 True False 5h24m Cluster version is 4.5.0-0.nightly-2020-05-24-223848 $ oc explain apiservers.spec KIND: APIServer VERSION: config.openshift.io/v1 RESOURCE: spec <Object> DESCRIPTION: spec holds user settable values for configuration ... DESCRIPTION was not empty, so move the bug verified.
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-2020:2409