-
Bug
-
Resolution: Done
-
Critical
-
None
-
ACM 2.14.0
-
None
-
False
-
-
False
-
-
-
Important
-
None
Description of problem:
flightctl-secrets pod fails to pull its image, causing the other flightctl pod's CreateContainerConfigError status.
Version-Release number of selected component (if applicable):
2.14.0-DOWNSTREAM-2025-06-05-04-29-38
How reproducible:
100%
Steps to Reproduce:
- Enable the edge manager component
- Check the flightctl pod status in ocm namespace
Actual results:
flightctl-secrets pod fails to pull its image, so the component is not usable
Warning Failed 70m (x5 over 73m) kubelet Failed to pull image "quay.io:443/acm-d/ose-cli-artifacts-rhel9@sha256:08912406afb80efdde879441e729084e214ba89d1aee4b648310aa438711f5ae": initializing source docker://quay.io:443/acm-d/ose-cli-artifacts-rhel9@sha256:08912406afb80efdde879441e729084e214ba89d1aee4b648310aa438711f5ae: reading manifest sha256:08912406afb80efdde879441e729084e214ba89d1aee4b648310aa438711f5ae in quay.io:443/acm-d/ose-cli-artifacts-rhel9: manifest unknown Warning Failed 70m (x5 over 73m) kubelet Error: ErrImagePull Normal BackOff 3m3s (x306 over 73m) kubelet Back-off pulling image "quay.io:443/acm-d/ose-cli-artifacts-rhel9@sha256:08912406afb80efdde879441e729084e214ba89d1aee4b648310aa438711f5ae" Warning Failed 3m3s (x306 over 73m) kubelet Error: ImagePullBackOff
Expected results:
After enabling the edge manager component, all the flightctl pods should become ready
