-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
ACM 2.14.0
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
-
Important
-
None
Description of problem:
CAPI and CAPA do not work in the current version of the Community Edition build of ACM.
Version-Release number of selected component (if applicable):
0.7.0
How reproducible:
Always
Steps to Reproduce:
- Install the Community Edition build of ACM
- Enable CAPI (note the error in the pod events)
- Enable CAPA (note the error in the pod events)
Actual results:
The following errors are thrown.
CAPI:
Failed to pull image "quay.io/stolostron/ose_cluster_api_rhel9@sha256:5bdd5905d5a6c6a611df6bf0aa0caf22eb768c938b52ae6a733ed5277c6e1c22": initializing source docker://quay.io/stolostron/ose_cluster_api_rhel9@sha256:5bdd5905d5a6c6a611df6bf0aa0caf22eb768c938b52ae6a733ed5277c6e1c22: reading manifest sha256:5bdd5905d5a6c6a611df6bf0aa0caf22eb768c938b52ae6a733ed5277c6e1c22 in quay.io/stolostron/ose_cluster_api_rhel9: unauthorized: access to the requested resource is not authorized
CAPA:
Failed to pull image "quay.io/stolostron/ose_aws_cluster_api_controllers_rhel9@sha256:5bdd5905d5a6c6a611df6bf0aa0caf22eb768c938b52ae6a733ed5277c6e1c22": initializing source docker://quay.io/stolostron/ose_aws_cluster_api_controllers_rhel9@sha256:5bdd5905d5a6c6a611df6bf0aa0caf22eb768c938b52ae6a733ed5277c6e1c22: reading manifest sha256:5bdd5905d5a6c6a611df6bf0aa0caf22eb768c938b52ae6a733ed5277c6e1c22 in quay.io/stolostron/ose_aws_cluster_api_controllers_rhel9: unauthorized: access to the requested resource is not authorized
Expected results:
Everything should work.
Additional info:
NA