Bug 1688638
| Summary: | Some CRDs of config.openshift.io apiversion with the 'oc explain` command will return empty info | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | zhou ying <yinzhou> |
| Component: | Master | Assignee: | Maciej Szulik <maszulik> |
| Status: | CLOSED ERRATA | QA Contact: | zhou ying <yinzhou> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.1.0 | CC: | aos-bugs, erich, hongli, jokerman, maszulik, mfojtik, mmccomas, sponnaga |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-04 10:45:49 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: | |||
We at least need the following PRs to land: - https://github.com/openshift/cluster-openshift-apiserver-operator/pull/158 - https://github.com/openshift/cluster-kube-apiserver-operator/pull/273 - https://github.com/openshift/cluster-config-operator/pull/27 Maybe more is needed, but I need to land those first. I think we're in a good state now, let's move to QA for verification. Confirmed with latest version : [root@dhcp-140-138 roottest]# oc version --short Client Version: v4.0.22 Server Version: v1.12.4+87e98f4 Payload: 4.0.0-0.nightly-2019-03-27-213938 The CRD :clusteroperator and clusterversion still don't have any information. [root@dhcp-140-138 roottest]# oc explain clusteroperators --api-version="config.openshift.io/v1"
KIND: ClusterOperator
VERSION: config.openshift.io/v1
DESCRIPTION:
<empty>
[root@dhcp-140-138 roottest]# oc explain clusterversions --api-version="config.openshift.io/v1"
KIND: ClusterVersion
VERSION: config.openshift.io/v1
DESCRIPTION:
<empty>
Tested with latest 4.0.0-0.nightly-2019-04-10-182914 and `oc explain` always returning "error: Couldn't find resource for <some resources>", see examples below: $ oc explain console --api-version=config.openshift.io/v1 error: Couldn't find resource for "config.openshift.io/v1, Kind=Console" $ oc explain IngressController error: Couldn't find resource for "operator.openshift.io/v1, Kind=IngressController" $ oc explain IngressController --api-version=operator.openshift.io/v1 error: Couldn't find resource for "operator.openshift.io/v1, Kind=IngressController" $ oc explain alertmanager error: Couldn't find resource for "monitoring.coreos.com/v1, Kind=Alertmanager" $ oc explain alertmanager --api-version=monitoring.coreos.com/v1 error: Couldn't find resource for "monitoring.coreos.com/v1, Kind=Alertmanager" $ oc explain InstallPlan error: Couldn't find resource for "operators.coreos.com/v1alpha1, Kind=InstallPlan" $ oc explain InstallPlan --api-version=operators.coreos.com/v1alpha1 error: Couldn't find resource for "operators.coreos.com/v1alpha1, Kind=InstallPlan" $ oc explain HostSubnet --api-version=network.openshift.io/v1 error: Couldn't find resource for "network.openshift.io/v1, Kind=HostSubnet" *** This bug has been marked as a duplicate of bug 1695176 *** There are more stuff to fix than just that openapi CRD mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1695176, reopening. *** Bug 1698644 has been marked as a duplicate of this bug. *** Verified on 4.1.0-0.okd-2019-04-19-102439 the following are ok: - oc explain console - oc explain IngressController - oc explain alertmanager - oc explain InstallPlan - oc explain HostSubnet ClusterOperator and ClusterVersion should be fixed in https://github.com/openshift/cluster-version-operator/pull/168 Confirmed with latest oc client , the issue has fixed:
[root@192 ~]# oc version
Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.0", GitCommit:"05c6cd644", GitTreeState:"clean", BuildDate:"2019-05-04T16:58:50Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+d4a26b6", GitCommit:"d4a26b6", GitTreeState:"clean", BuildDate:"2019-05-04T18:12:07Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
[root@192 ~]# oc explain clusteroperators --api-version="config.openshift.io/v1"
KIND: ClusterOperator
VERSION: config.openshift.io/v1
DESCRIPTION:
<empty>
FIELDS:
apiVersion <string>
APIVersion defines the versioned schema of this representation of an
object. Servers should convert recognized schemas to the latest internal
value, and may reject unrecognized values. More info:
https://git.k8s.io/community/contributors/devel/api-conventions.md#resources
kind <string>
Kind is a string value representing the REST resource this object
represents. Servers may infer this from the endpoint the client submits
requests to. Cannot be updated. In CamelCase. More info:
https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds
metadata <Object>
Standard object's metadata. More info:
https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata
spec <map[string]> -required-
spec hold the intent of how this operator should behave.
status <Object>
status holds the information about the state of an operator. It is
consistent with status information across the kube ecosystem.
[root@192 ~]# oc explain clusterversions --api-version="config.openshift.io/v1"
KIND: ClusterVersion
VERSION: config.openshift.io/v1
DESCRIPTION:
<empty>
FIELDS:
apiVersion <string>
APIVersion defines the versioned schema of this representation of an
object. Servers should convert recognized schemas to the latest internal
value, and may reject unrecognized values. More info:
https://git.k8s.io/community/contributors/devel/api-conventions.md#resources
kind <string>
Kind is a string value representing the REST resource this object
represents. Servers may infer this from the endpoint the client submits
requests to. Cannot be updated. In CamelCase. More info:
https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds
metadata <Object>
Standard object's metadata. More info:
https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata
spec <Object> -required-
spec is the desired state of the cluster version - the operator will work
to ensure that the desired version is applied to the cluster.
status <Object>
status contains information about the available updates and any in-progress
updates.
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 |
Description of problem: Some CRD of config.openshift.io like: clusteroperators/clusterversions/dnses/networks/registries, when use the 'oc explain' command, will return nothing Version-Release number of selected component (if applicable): Client Version: v4.0.22 Server Version: v1.12.4+4836bc9 Payload version:4.0.0-0.nightly-2019-03-13-233958 How reproducible: Always Steps to Reproduce: 1. Use the command `oc explain` with the CRD of config.openshift.io like: clusteroperators/clusterversions/dnses/networks/registries Actual results: 1. The DESCRIPTION of output always empty and no FIELDS: oc explain registries KIND: Registry VERSION: config.openshift.io/v1 DESCRIPTION: <empty> Expected results: 1. Have detail info for the CRD of config.openshift.io Additional info: Other CRD like: projects, works well. oc explain projects --api-version="config.openshift.io/v1" KIND: Project VERSION: config.openshift.io/v1 DESCRIPTION: <empty> FIELDS: apiVersion <string> APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#resources kind <string> Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds metadata <Object> Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata spec <Object> -required- spec holds user settable values for configuration status <map[string]> status holds observed values from the cluster. They may not be overridden.