-
Bug
-
Resolution: Done
-
Undefined
-
4.15.0
-
None
-
No
-
Hypershift Sprint 242, Hypershift Sprint 243, Hypershift Sprint 244
-
3
-
False
-
Description of problem:
The cloud network config controller never initializes on Azure HostedClusters. This behaviors exists on both Arm and x86 Azure mgmt clusters.
Version-Release number of selected component (if applicable):
How reproducible:
Every time
Steps to Reproduce:
1. Create either an Arm or x86 Azure mgmt cluster 2. Install HO 3. Create a HostedCluster 4. Observe CNCC pod doesn't initialize
Actual results:
CNCC pod doesn't initialize
Expected results:
CNCC pod initializes
Additional info:
It looks like a secret isn't being reconciled to the CPO % oc describe pod/cloud-network-config-controller-96567b45f-7jkl5 -n clusters-brcox-hypershift-arm Name: cloud-network-config-controller-96567b45f-7jkl5 ... Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 5m46s default-scheduler Successfully assigned clusters-brcox-hypershift-arm/cloud-network-config-controller-96567b45f-7jkl5 to ci-ln-vmb5w8k-1d09d-jr6m6-worker-centralus3-45dg5 Warning FailedMount 101s (x2 over 3m44s) kubelet Unable to attach or mount volumes: unmounted volumes=[cloud-provider-secret], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition Warning FailedMount 97s (x10 over 5m47s) kubelet MountVolume.SetUp failed for volume "cloud-provider-secret" : secret "cloud-network-config-controller-creds" not found
