URL:
Reporter RHNID:
Section: -
Language: en-US (English)
Workaround:

Description: I've taught this course many times - I am not new to it's nuances.

As part of my demonstration I deployed ACM, I did not run lab start multicluster-acm as I do not need to. As part of the onboarding, I demonstrated `./wait.sh` and `ocp4-mng/wait.sh` so I knew that my cluster was available and ready to deploy ACM. It took a significant amount of time to deploy and then took a long time for the cluster operators to stabilize.

I deployed ACM, and ran `oc get route -n open-cluster-management` at 03:58:36 and I was only able to login at 04:14:34 to validate that the route is created. Only then could I go to the ACM console to start the import process of the managed cluster. There are 30 minutes allocated to the entire activity. I've delivered this course many times and this behaviour is not normal. While I was filing this very Jira I've had 4 other complaints from students that they're just waiting and wanted to know if there is a problem.

I hope that there is collaboration between the curriculum team and platform team to review the architecture so that we can avoid negative feedback from customers. We do our best in front of the customers to keep them happy ... and calm but we need external support on this issue.