Welcome to the Managing Virtual Machines with Red Hat OpenShift (DO316) course in RHLC!

[Syed]

We are excited to launch a space dedicated to the Red Hat Training course, Managing Virtual Machines with Red Hat OpenShift Virtualization!

To gain the most value from this group - click the "Join Group" button in the upper right hand corner of the group home page.

We encourage group members to collaborate in this group to discuss topics, ask questions, share best practices and tips, provide course feedback, and share their accomplishments as it relates to DO316.

Read more about Managing Virtual Machines with Red Hat OpenShift Virtualization here.

[bchardim]

Hi andywalk,

Are you still facing those issues ? I am running https://rol.redhat.com/rol/app/courses/do316-4.16/pages/ch02s04 lan env in EMEA region, and I am not seeing any issue. In which region are you running your lab env ?

Attached, you can see my screenshots.

Preview

[andywalk]

I am in the northeast region. New Jersey

On Tue, Oct 21, 2025 at 11:30 AM Wayne A. Walker
wrote:

> Hello,
> I tried just over an hour ago and still am experiencing the issue. I
> recall typing
> "lab start -t d0316 accessing-review" on the workstation and then seeing
> the issue.
>

[bchardim]

Weird, I can not reproduce the issue. For me, it is working as expected, as you can see from my screenshots.

Please, can you try the following:

1.- Re-create your do316-4.16 PROD lab env

2.- Run the wait.sh script and wait.

3.- Test again the "lab start -t d0316 accessing-review" exec from workstation

Then share here the following,

* URL of your new lab env (mine is https://rol.redhat.com/rol/app/courses/do316-4.16/pages/ch02s04)

* Screenshot with your lab information displayed, as the screenshot that I have attached.

* Screenshot of the result of executing lab start -t d0316 accessing-review from workstation,  as the screenshot that I have attached.

Thanks!

[Chetan_Tiwary_]

@andywalk The best way to reach out for support during such issues is to raise a support case so that the backend support can check your lab and help you. 

[andywalk]

Thanks Chetan,
I finally got it to work after deleting the environment and re-creating the
machines, following by multiple attempts to start the lab, long after the
GUI listed the servers as "Active". Below is what I sent to a user that
tried to help me out. I think I am okay now. Next time I will engage the
support as you suggested.

I finally got it to work by first deleting my environment and starting
afresh. Then it took a few tries to get going, as long after it told me
that all the machines were started and "Active", the console still gave me
messages that had me wait up to close to thirty minutes afterwards. Then
finally it started.
Below is the error file I had it create when I used a command such as " lab
logs accessing-review > error.txt".
[image: Pasted Graphic.png]

[image: Pasted Graphic 2.png]


This is when it stated working

[image: Pasted Graphic 3.png]
Now it is seemingly working as I make my way through the questions up to
2.1 of the first lab. Unfortunately I have lost more than four hours of
lab time that I never got, as previously it was not starting. Thanks for
taking some time to send me suggestions. I really appreciate it.

[Chetan_Tiwary_]

Great news @andywalk glad that your issue is resolved and you can continue your learning!