-
Bug
-
Resolution: Done
-
Major
-
None
-
AD482 - RHAMQS1.8-en-5-20221213
-
None
-
False
-
-
False
-
4
-
en-US (English)
Please fill in the following information:
Issue description
Starting with chapter 4, but sometimes even earlier, "lab start" scripts create a large number of KafkaTopic resources using the apply_template_and_wait() method of ocpcli.client, sequentially, which means every create operation first waits for the single topic to be ready before moving on to next one.
Unfortunately, with the shared cluster, the default timeout of 120 seconds is always too low and most of the time even the first topic creation will timeout waiting for a ready condition, not to mention that even if they were to succeed within the two minutes, for 6 topics (such as stateless processing exercise creates) that means around 12 minutes wait.
What this also means is that students can of course re-run the script as many times as there are topics, but that will just consume excessive amounts of time and require students' attention for around 15-20 minutes before they can start the exercise.
A partial solution is either to invoke apply_template_and_wait with a longer timeout_seconds parameter (something like 600), and have the students run the "lab start" script at the beginning of the lecture.
The long-term solution is to parallelise the topic creation and have the _wait part of the ocpcli.client module check all the resources for status after that.