-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
DO480 - ACM2.4-en-5-20221130
-
None
-
False
-
-
False
-
-
-
en-US (English)
Please fill in the following information:
URL: | |
Reporter RHNID: | |
Section Title: |
Issue description
Any lab script in the start section tries to check whether ACM is installed or not.
Among these checks, it looks for an operator group named acm-operatorgroup on the hub cluster in the open-cluster-management project.
This operator groyp does not exist when you use OperatorHub and it might hang eternally waiting until it is deleted.
When you use OperatorHub an operatorgroup named open-cluster-management-xxxx is created instead.
Steps to reproduce:
Start the GE Installing Red Hat Advanced Cluster Management for Kubernetes, without deleting the ACM instance created. Then run the following GE ({}
Navigating the RHACM Web Console). The lab start hangs indefinitely.
Workaround:
Delete the operator-group mentioned before.
Expected result: