-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.14.z
This is a clone of issue OCPBUGS-45040. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-45039. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-41903. The following is the description of the original issue:
—
Description of problem:
OCP cluster upgrade is stuck with image registry pod in degraded state. The image registry co shows the below error message. - lastTransitionTime: "2024-09-13T03:15:05Z" message: "Progressing: All registry resources are removed\nNodeCADaemonProgressing: The daemon set node-ca is deployed\nAzurePathFixProgressing: Migration failed: I0912 18:18:02.117077 1 main.go:233] Azure Stack Hub environment variables not present in current environment, skipping setup...\nAzurePathFixProgressing: panic: Get \"https://xxxxximageregistry.blob.core.windows.net/xxxxcontainer?comp=list&prefix=docker&restype=container\": dial tcp: lookup xxxximageregistry.blob.core.windows.net on 192.168.xx.xx. no such host\nAzurePathFixProgressing: \nAzurePathFixProgressing: goroutine 1 [running]:\nAzurePathFixProgressing: main.main()\nAzurePathFixProgressing: \t/go/src/github.com/openshift/cluster-image-registry-operator/cmd/move-blobs/main.go:53 +0x12a\nAzurePathFixProgressing: " reason: AzurePathFixFailed::Removed status: "False" type: Progressing
Version-Release number of selected component (if applicable):
4.14.33
How reproducible:
Steps to Reproduce:
1. configure azure storage in configs.imageregistry.operator.openshift.io/cluster
2. then mark the managementState as Removed
3. check the operator status
Actual results:
CO image-registry remain is degraded state
Expected results:
Operator should not be in degraded state
Additional info:
- clones
-
-
- New
-
- is blocked by
-
-
- New
-
- links to
