Currently, our controllers enforce some values in cluster object specs, this might not work for UPI. We should drop most of the logic and also remove validating webhooks so we can use clusters in a more flexible way.
Hi@ademicev wanted to get results reviewed , do you think this is expected and any other need to check? Tested on gcp, clusterversion 4.11.0-0.nightly-2022-06-14-032134 Cluster and InfrastructureCluter are not created, feel there is some issue here, or have I missed something? $ oc get clusters.cluster.x-k8s.io --all-namespaces No resources found $ oc get gcpclusters.infrastructure.cluster.x-k8s.io --all-namespaces No resources found No cluster related webhooks. $ oc get mutatingwebhookconfigurations -n openshift-cluster-api NAME WEBHOOKS AGE capg-mutating-webhook-configuration 2 126m capi-mutating-webhook-configuration 5 126m machine-api 2 4h45m $ oc get validatingwebhookconfigurations -n openshift-cluster-api NAME WEBHOOKS AGE alertmanagerconfigs.openshift.io 1 4h32m autoscaling.openshift.io 2 4h47m capg-validating-webhook-configuration 2 129m capi-validating-webhook-configuration 6 129m machine-api 2 4h48m multus.openshift.io 1 4h49m performance-addon-operator 1 4h51m prometheusrules.openshift.io 1 4h32m snapshot.storage.k8s.io 1 4h48m
As no Cluster and InfrastructureCluter are created, move this back, if I am wrong, feel free move to ON_QA
Hi, Cluster and InfrastructureCluter are expected to be created by users, not by the operator.
Move to verified, test on upi aws, create cluster and awscluster works well, annotation can be set and cluster status can be update. clusterversion: 4.11.0-0.nightly-2022-06-28-160049 status: conditions: - lastTransitionTime: "2022-06-30T05:17:05Z" status: "True" type: Ready - lastTransitionTime: "2022-06-30T04:04:34Z" status: "True" type: ControlPlaneInitialized - lastTransitionTime: "2022-06-30T05:17:05Z" status: "True" type: InfrastructureReady infrastructureReady: true observedGeneration: 1 phase: Provisioning apiVersion: infrastructure.cluster.x-k8s.io/v1beta1 kind: AWSCluster metadata: annotations: cluster.x-k8s.io/managed-by: "" creationTimestamp: "2022-06-30T05:17:05Z" generation: 1 labels: cluster.x-k8s.io/cluster-name: zhsunupi-h8wbm name: zhsunupi-h8wbm namespace: openshift-cluster-api ownerReferences: - apiVersion: cluster.x-k8s.io/v1beta1 blockOwnerDeletion: true controller: true kind: Cluster name: zhsunupi-h8wbm uid: 698ab64a-6983-4336-a38c-2f1cafce838d resourceVersion: "91736" uid: 6addd3b2-7cd3-46a9-9427-ec9fcc3731f7 spec: region: us-east-2 status: ready: true
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. https://access.redhat.com/errata/RHSA-2022:5069