Description of problem: Executing oc explain storagestates and storageversionmigrations with empty DESCRIPTION Version-Release number of selected component (if applicable): $ oc version -o yaml clientVersion: buildDate: "2020-02-28T23:32:38Z" compiler: gc gitCommit: bc08a48555986f64165555efd2705eff7ef2de81 gitTreeState: clean gitVersion: 4.4.0-202002282323-bc08a48 goVersion: go1.13.4 major: "" minor: "" platform: linux/amd64 openshiftVersion: 4.4.0-0.nightly-2020-03-02-074928 serverVersion: buildDate: "2020-03-02T05:46:10Z" compiler: gc gitCommit: "7303e47" gitTreeState: clean gitVersion: v1.17.1 goVersion: go1.13.4 major: "1" minor: "17" platform: linux/amd64 How reproducible: Always Actual results: $ oc explain storagestates.migration.k8s.io KIND: StorageState VERSION: migration.k8s.io/v1alpha1 DESCRIPTION: <empty> $ oc explain storageversionmigrations.migration.k8s.io KIND: StorageVersionMigration VERSION: migration.k8s.io/v1alpha1 DESCRIPTION: <empty> Expected results: Since we can get the detail from ‘oc get crd storagestates.migration.k8s.io/storageversionmigrations.migration.k8s.io -o yaml ’, it's easy with detail for DESCRIPTION ‘oc explain storagestates/storageversionmigrations’. 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.
Checked with latest OCP 4.5, still not fixed. $ oc version Client Version: 4.5.0-202005181857-67da73a Server Version: 4.5.0-0.nightly-2020-05-19-011623 Kubernetes Version: v1.18.2 $ oc explain storagestates.migration.k8s.io KIND: StorageState VERSION: migration.k8s.io/v1alpha1 DESCRIPTION: <empty> $ oc explain storageversionmigrations.migration.k8s.io KIND: StorageVersionMigration VERSION: migration.k8s.io/v1alpha1 DESCRIPTION: <empty>
$ oc adm release info --commits registry.svc.ci.openshift.org/ocp/release:4.5.0-0.nightly-2020-06-15-194331 | grep kube-storage-version-migrator cluster-kube-storage-version-migrator-operator https://github.com/openshift/cluster-kube-storage-version-migrator-operator 8aa9246a10831ea08a5f8d3d9ba342285cca7705 ... $ git log --date local --pretty="%h %an %cd - %s" 8aa9246a10831ea08a5f8d3d9ba342285cca7705 | grep '#22' The PR has not been merged, wait for the next.
$ oc adm release info --commits registry.svc.ci.openshift.org/ocp/release:4.5.0-0.nightly-2020-06-19-024326 | grep kube-storage-version-migrator-operator cluster-kube-storage-version-migrator-operator https://github.com/openshift/cluster-kube-storage-version-migrator-operator 8aa9246a10831ea08a5f8d3d9ba342285cca7705 $ git log --date local --pretty="%h %an %cd - %s" 8aa9246a | grep '#22' The related PR #22 still has not been merged into latest OCP 4.5 payload.
The PR is 4.6 PR. I think our Dev Luis does not notice the Target Release should match the PR branch. Considering this is a low issue, correcting target release to 4.6 and moving to VERIFIED after checking latest 4.6 payload env.
Verifed with OCP 4.6.0-0.nightly-2020-06-26-035408, see below, $ oc explain storagestates --api-version=migration.k8s.io/v1alpha1 KIND: StorageState VERSION: migration.k8s.io/v1alpha1 DESCRIPTION: The state of the storage of a specific resource. 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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds metadata <Object> Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata spec <Object> Specification of the storage state. status <Object> Status of the storage state. $ oc explain storageversionmigrations --api-version=migration.k8s.io/v1alpha1 KIND: StorageVersionMigration VERSION: migration.k8s.io/v1alpha1 DESCRIPTION: StorageVersionMigration represents a migration of stored data to the latest storage version. 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/sig-architecture/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/sig-architecture/api-conventions.md#types-kinds metadata <Object> Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata spec <Object> Specification of the migration. status <Object> Status of the migration.
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.5 image release 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