-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
4.16.0
-
No
-
Hypershift Sprint 251, Hypershift Sprint 252, Hypershift Sprint 253
-
3
-
False
-
-
Release Note Not Required
-
In Progress
This is a clone of issue OCPBUGS-30060. The following is the description of the original issue:
—
Description of problem:
The image registry CO is not progressing on Azure Hosted Control Planes
Version-Release number of selected component (if applicable):
How reproducible:
Every time
Steps to Reproduce:
1. Create an Azure HCP
2. Create a kubeconfig for the guest cluster
3. Check the image-registry CO
Actual results:
image-registry co's message is Progressing: The registry is ready...
Expected results:
image-registry finishes progressing
Additional info:
I let it go for about 34m
% oc get co | grep -i image
image-registry 4.16.0-0.nightly-multi-2024-02-26-105325 True True False 34m Progressing: The registry is ready...
% oc get co/image-registry -oyaml
...
- lastTransitionTime: "2024-02-28T19:10:30Z"
message: |-
Progressing: The registry is ready
NodeCADaemonProgressing: The daemon set node-ca is deployed
AzurePathFixProgressing: The job does not exist
reason: AzurePathFixNotFound::Ready
status: "True"
type: Progressing
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to