master PR @ https://github.com/openshift/cluster-network-operator/pull/592
PR has been merged, moving to ON-QE
Verified failed on both 4.4 and 4.5 oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.4.0-0.nightly-2020-05-08-040144 True False 40m Cluster version is 4.4.0-0.nightly-2020-05-08-040144 oc explain network-attachment-definitions KIND: NetworkAttachmentDefinition VERSION: k8s.cni.cncf.io/v1 DESCRIPTION: <empty> oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.0-0.nightly-2020-05-07-144853 True False 4h57m Cluster version is 4.5.0-0.nightly-2020-05-07-144853 oc explain network-attachment-definitions KIND: NetworkAttachmentDefinition VERSION: k8s.cni.cncf.io/v1 DESCRIPTION: <empty>
I now believe that this may not actually be possible for NetworkAttachmentDefinitions. I mistakenly assumed that `oc explain` would use `description` fields from CRDs -- however, that doesn't seem to be the case. It appears that oc explain reads from openshift/api (at least from finding references to other stuff that appears in oc explain in the api, for example `oc explain networks` I can see the text from that output in this PR: https://github.com/openshift/api/pull/381/files ) -- and the NetworkAttachmentDefinition is not in the api, but, is a CRD. You can get the description fields by doing a `oc describe crd network-attachment-definitions.k8s.cni.cncf.io` Compare/contrast: networks.config.openshift.io -- in the openshift API, network-attachment-definitions.k8s.cni.cncf.io -- not in the openshift API. Potentially `oc explain` could be enhanced to describe CRDs, however that's outside of the scope of this request, I believe. ...I think this should actually be closed in this case. Any other input before I close?
Tomo has updates ready for downstream 4.4 in https://github.com/openshift/cluster-network-operator/pull/735
Removing the dependency on the 4.6 bug because the bot complains, it's dependent only on the 4.5 bug (BZ#1861412)
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 (OpenShift Container Platform 4.4.23 bug fix update), 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:3715