Description of problem: Installed OCP 4.8.2 using the single-node-developer profile: $ export OPENSHIFT_INSTALL_EXPERIMENTAL_CLUSTER_PROFILE=single-node-developer $ oc create manifests $ oc create ignition-configs Version-Release number of selected component (if applicable): 4.8.2, link https://mirror.openshift.com/pub/openshift-v4/clients/ocp/4.8.2/ How reproducible: Just install OpenShift 4.8.2 using the single-node-developer profile Actual results: The console cluster operator won't become available: $ oc get clusteroperator NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE authentication 4.8.2 True False False 23m baremetal cluster-autoscaler 4.8.2 True False False 39m config-operator 4.8.2 True False False 40m console 4.8.2 False False False 32m csi-snapshot-controller 4.8.2 True False False 40m dns 4.8.2 True False False 40m etcd 4.8.2 True False False 39m image-registry 4.8.2 True False False 33m ingress 4.8.2 True False False 34m insights 4.8.2 True False False 33m kube-apiserver 4.8.2 True False True 35m kube-controller-manager 4.8.2 True False False 39m kube-scheduler 4.8.2 True False False 36m machine-api 4.8.2 True False False 39m machine-approver 4.8.2 True False False 40m machine-config 4.8.2 True False False 39m marketplace 4.8.2 True False False 39m monitoring 4.8.2 True False False 31m network 4.8.2 True False False 41m node-tuning 4.8.2 True False False 39m openshift-apiserver 4.8.2 True False False 33m openshift-controller-manager 4.8.2 True False False 39m openshift-samples 4.8.2 True False False 32m operator-lifecycle-manager 4.8.2 True False False 40m operator-lifecycle-manager-catalog 4.8.2 True False False 40m operator-lifecycle-manager-packageserver 4.8.2 True False False 33m service-ca 4.8.2 True False False 40m storage 4.8.2 True False False 40m Console pod is not deployed at all. Expected results: The console cluster operator should deploy console. Additional info: This issue is caused by the cluster-version-operator not deploying consoleplugin CRD. After applying this CRD manually to the cluster, the console is deployed and the console operator becomes available. This is the command that fixes the issue for me: $ oc rsh -n openshift-cluster-version cluster-version-operator-789d46ff9d-lbcn4 cat /release-manifests/0000_10_consoleplugin.crd.yaml | oc apply -f - customresourcedefinition.apiextensions.k8s.io/consoleplugins.console.openshift.io created
@Ales are you available to help to try the fix from your side?
(In reply to Yanping Zhang from comment #3) > @Ales are you available to help to try the fix from your side? Yes, I can test the fix. What should I do?
@Ales, thanks for your help, will tell you when we get the exact info about the but test. @Jakub or @Sam, I noticed the fix in pr https://github.com/openshift/api/pull/980/files is not bumped into console-operator repo, the file console-operator/vendor/github.com/openshift/api/console/v1alpha1/0000_10_consoleplugin.crd.yaml doesn't contain the update from pr980. Could you help to check?
Moving back to assigned. We still need to bump openshift/api in the console-operator.
Launched SNO cluster with payload 4.9.0-0.nightly-2021-08-30-192239, all cluster operators are installed successfully, and check annotation in the ConsolePlugin CRD yaml, there is new annotation added: include.release.openshift.io/single-node-developer: 'true'
After discussed with Jakub, the test in Comment 8 is correct to verify this bug, so move the bug to Verified. Thanks all!
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security 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/RHSA-2021:3759
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days