PR #7430 - 01-09 07:05

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-2t5zq/autoscaling-z4vvn in 57s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-z4vvn util.go:2949: Successfully waited for HostedCluster e2e-clusters-2t5zq/autoscaling-z4vvn to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-2t5zq/autoscaling-z4vvn in 1m27s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-z4vvn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-z4vvn.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-z4vvn.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.209.9.220:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m29.225s util.go:565: Successfully waited for 1 nodes to become ready in 7m27s util.go:598: Successfully waited for HostedCluster e2e-clusters-2t5zq/autoscaling-z4vvn to rollout in 3m48s util.go:2949: Successfully waited for HostedCluster e2e-clusters-2t5zq/autoscaling-z4vvn to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-2t5zq/autoscaling-z4vvn in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-677f4d8cc7-ng587 has a restartCount > 0 (6)

create_cluster_test.go:2492: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-vslmg/create-cluster-bqhmc in 54s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-bqhmc util.go:2949: Successfully waited for HostedCluster e2e-clusters-vslmg/create-cluster-bqhmc to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-vslmg/create-cluster-bqhmc in 1m36s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-bqhmc.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-bqhmc.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-bqhmc.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.48.134.137:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m34.025s util.go:565: Successfully waited for 3 nodes to become ready in 8m12s util.go:598: Successfully waited for HostedCluster e2e-clusters-vslmg/create-cluster-bqhmc to rollout in 3m15s util.go:2949: Successfully waited for HostedCluster e2e-clusters-vslmg/create-cluster-bqhmc to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-vslmg/create-cluster-bqhmc in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-58cb54658-7f42q has a restartCount > 0 (6)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-stzjx/custom-config-f2bw5 in 40s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-f2bw5 util.go:2949: Successfully waited for HostedCluster e2e-clusters-stzjx/custom-config-f2bw5 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-stzjx/custom-config-f2bw5 in 1m39s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f2bw5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-f2bw5.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f2bw5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 107.21.4.45:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f2bw5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.205.138.120:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f2bw5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.205.138.120:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f2bw5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 107.21.4.45:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f2bw5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.205.138.120:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f2bw5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 107.21.4.45:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f2bw5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.205.138.120:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f2bw5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 107.21.4.45:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f2bw5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.205.138.120:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f2bw5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 107.21.4.45:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-f2bw5.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 18.205.138.120:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m48.025s util.go:565: Successfully waited for 2 nodes to become ready in 6m51s util.go:598: Successfully waited for HostedCluster e2e-clusters-stzjx/custom-config-f2bw5 to rollout in 7m33s util.go:2949: Successfully waited for HostedCluster e2e-clusters-stzjx/custom-config-f2bw5 to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-stzjx/custom-config-f2bw5 in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-7dcdd48d6f-wlwlq has a restartCount > 0 (7)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-7fzdf/private-42svd in 28s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-42svd util.go:2949: Successfully waited for HostedCluster e2e-clusters-7fzdf/private-42svd to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7fzdf/private-42svd in 1m33s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-7fzdf/private-42svd to have all of their desired nodes in 10m45s util.go:598: Successfully waited for HostedCluster e2e-clusters-7fzdf/private-42svd to rollout in 8m39s util.go:2949: Successfully waited for HostedCluster e2e-clusters-7fzdf/private-42svd to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7fzdf/private-42svd in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-7f979f6fcc-d9k88 has a restartCount > 0 (8)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-lk76f/private-bw99t in 36s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-bw99t util.go:2949: Successfully waited for HostedCluster e2e-clusters-lk76f/private-bw99t to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-lk76f/private-bw99t in 1m45s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-lk76f/private-bw99t to have all of their desired nodes in 9m30s util.go:598: Successfully waited for HostedCluster e2e-clusters-lk76f/private-bw99t to rollout in 5m54s util.go:2949: Successfully waited for HostedCluster e2e-clusters-lk76f/private-bw99t to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-lk76f/private-bw99t in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-f5689dd6f-qrghg has a restartCount > 0 (7)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-vfpmk/proxy-lwmxs in 26s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-lwmxs util.go:2949: Successfully waited for HostedCluster e2e-clusters-vfpmk/proxy-lwmxs to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-vfpmk/proxy-lwmxs in 1m36s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-lwmxs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-lwmxs.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-lwmxs.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 100.31.12.35:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m20.125s util.go:565: Successfully waited for 2 nodes to become ready in 8m39s util.go:598: Successfully waited for HostedCluster e2e-clusters-vfpmk/proxy-lwmxs to rollout in 6m24s util.go:2949: Successfully waited for HostedCluster e2e-clusters-vfpmk/proxy-lwmxs to have valid conditions in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-vfpmk/proxy-lwmxs in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-5fd66b7d9c-db4g2 has a restartCount > 0 (7)

requestserving.go:105: Created request serving nodepool clusters/aa34ff510b6a82cabb09-mgmt-reqserving-fzhxh requestserving.go:105: Created request serving nodepool clusters/aa34ff510b6a82cabb09-mgmt-reqserving-p2sgx requestserving.go:113: Created non request serving nodepool clusters/aa34ff510b6a82cabb09-mgmt-non-reqserving-9qk5x requestserving.go:113: Created non request serving nodepool clusters/aa34ff510b6a82cabb09-mgmt-non-reqserving-lhqqq requestserving.go:113: Created non request serving nodepool clusters/aa34ff510b6a82cabb09-mgmt-non-reqserving-zg469 util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/aa34ff510b6a82cabb09-mgmt-reqserving-fzhxh in 3m51s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/aa34ff510b6a82cabb09-mgmt-reqserving-p2sgx in 0s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/aa34ff510b6a82cabb09-mgmt-non-reqserving-9qk5x in 36s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/aa34ff510b6a82cabb09-mgmt-non-reqserving-lhqqq in 0s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/aa34ff510b6a82cabb09-mgmt-non-reqserving-zg469 in 0s create_cluster_test.go:2670: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-vr84x/request-serving-isolation-ds5ps in 22s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-ds5ps util.go:2949: Successfully waited for HostedCluster e2e-clusters-vr84x/request-serving-isolation-ds5ps to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/aa34ff510b6a82cabb09-mgmt-reqserving-fzhxh requestserving.go:132: Tearing down custom nodepool clusters/aa34ff510b6a82cabb09-mgmt-reqserving-p2sgx requestserving.go:132: Tearing down custom nodepool clusters/aa34ff510b6a82cabb09-mgmt-non-reqserving-9qk5x requestserving.go:132: Tearing down custom nodepool clusters/aa34ff510b6a82cabb09-mgmt-non-reqserving-lhqqq requestserving.go:132: Tearing down custom nodepool clusters/aa34ff510b6a82cabb09-mgmt-non-reqserving-zg469 hypershift_framework.go:230: skipping teardown, already called

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-vr84x/request-serving-isolation-ds5ps in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-6bc5c44797-xspcn has a restartCount > 0 (7)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-9qpg6/node-pool-zm4hh in 25s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-zm4hh util.go:2949: Successfully waited for HostedCluster e2e-clusters-9qpg6/node-pool-zm4hh to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9qpg6/node-pool-zm4hh in 1m45s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-zm4hh.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-zm4hh.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-zm4hh.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.88.215.93:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-zm4hh.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 44.205.126.41:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-zm4hh.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.88.215.93:443: connect: connection refused eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-zm4hh.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 54.87.85.119:443: connect: connection refused util.go:363: Successfully waited for a successful connection to the guest API server in 2m8.775s util.go:565: Successfully waited for 0 nodes to become ready in 0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-9qpg6/node-pool-zm4hh to have valid conditions in 2m15s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9qpg6/node-pool-zm4hh in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-7c64c9bc89-bzzrb has a restartCount > 0 (3)

hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-j7kgl/node-pool-5jm2f in 43s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-5jm2f util.go:2949: Successfully waited for HostedCluster e2e-clusters-j7kgl/node-pool-5jm2f to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-j7kgl/node-pool-5jm2f in 1m48s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-5jm2f.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-5jm2f.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-5jm2f.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.193.103.83:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-5jm2f.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.226.171.110:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m30.1s util.go:565: Successfully waited for 0 nodes to become ready in 25ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-j7kgl/node-pool-5jm2f to have valid conditions in 2m18s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-j7kgl/node-pool-5jm2f in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-7b95cdbc45-wnn7g has a restartCount > 0 (2)

control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-4pp7261g/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-4pp7261g/release@sha256:1c5d76ff3d6fd87e77b6991ebe9bb96e7b2328ae7db8e00f488af6bbc6d7e877 hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-kpswq/control-plane-upgrade-wz7gh in 26s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-wz7gh util.go:2949: Successfully waited for HostedCluster e2e-clusters-kpswq/control-plane-upgrade-wz7gh to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-kpswq/control-plane-upgrade-wz7gh in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:363: Successfully waited for a successful connection to the guest API server in 0s control_plane_upgrade_test.go:52: Updating cluster image. Image: registry.build01.ci.openshift.org/ci-op-4pp7261g/release@sha256:1c5d76ff3d6fd87e77b6991ebe9bb96e7b2328ae7db8e00f488af6bbc6d7e877 util.go:598: Successfully waited for HostedCluster e2e-clusters-kpswq/control-plane-upgrade-wz7gh to rollout in 0s

util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-kpswq/control-plane-upgrade-wz7gh in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-c46b76589-c47jw has a restartCount > 0 (8)

eventually.go:258: Failed to get **v1beta1.ControlPlaneComponent: client rate limiter Wait returned an error: context deadline exceeded util.go:638: Failed to wait for control plane components to complete rollout in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1beta1.ControlPlaneComponent state after 30m0s eventually.go:400: - observed **v1beta1.ControlPlaneComponent e2e-clusters-kpswq-control-plane-upgrade-wz7gh/cluster-network-operator invalid: eventually.go:403: - incorrect condition: wanted RolloutComplete=True, got RolloutComplete=False: WaitingForOperands(deployment cloud-network-config-controller is not ready) eventually.go:403: - component cluster-network-operator is still on version 4.22.0-0.ci-2026-01-08-185312 util.go:638: *v1beta1.ControlPlaneComponent e2e-clusters-kpswq-control-plane-upgrade-wz7gh/cluster-network-operator conditions: util.go:638: Available=True: AsExpected(Deployment cluster-network-operator is available) util.go:638: RolloutComplete=False: WaitingForOperands(deployment cloud-network-config-controller is not ready)