Description of problem:
Currently operator doesn't deploying resources after enabling TechPreviewNoUpgrade feature set.
Version-Release number of selected component (if applicable):
Often, almost always
Steps to Reproduce:
1. Deploy a cluster on AWS or any other platfrom with CCM support (https://github.com/openshift/cluster-cloud-controller-manager-operator#supported-platforms)
2. Enable TechPreviewNoUpgrade feature set: https://docs.openshift.com/container-platform/4.9/nodes/clusters/nodes-cluster-enabling-features.html
CCM operator doesn't deploy CCM resources, but KCM, Kubelet and API server are switched to external cloud providers.
2022-02-16 12:39:59+00:00 - Wait for CCCMO operands creation
2022-02-16 12:40:03+00:00 - Timed out waiting for result of CCMPodsCreated
CCM operator should deploy all required CCM resources
Example of a failed job:
After enabling TechPreviewNoUpgrade feature set, CCM resources are deployed.
$ oc get po -n openshift-cloud-controller-manager
NAME READY STATUS RESTARTS AGE
aws-cloud-controller-manager-754847c997-fgwg6 1/1 Running 0 28m
aws-cloud-controller-manager-754847c997-vspbx 1/1 Running 0 28m
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 (Important: OpenShift Container Platform 4.11.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.