cancel
Showing results for 
Search instead for 
Did you mean: 
Syed
Community Manager
Community Manager
  • 7,844 Views

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

Jump to solution

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.

Labels (5)
48 Replies
ipalagin
Flight Engineer Flight Engineer
Flight Engineer
  • 220 Views

Problems with do316:

wait.sh reports:

Screenshot 2024-12-27 at 18.49.50.png

 

But labs can't be started:

 

Screenshot 2024-12-27 at 18.50.52.png

On Dec 23, I opened a ticket regading another lab with the same issue, called "multihomed-review".  Received "thank you for submitting" and nothing since then.

 

Thanks,

Ilya.

 

eddielau
Flight Engineer
Flight Engineer
  • 200 Views

the easier way,i would advise you to destroy lab and recreate again, it have some potential like operator been installed or some VM, namespace, resources not cleanup, so it will cause this issue. 

ipalagin
Flight Engineer Flight Engineer
Flight Engineer
  • 15 Views

I used to think that destroying and re-creating the lab environment is a universal way to resolve any OpenShift lab issue. But at some point, support asked me why I destroyed the lab if I didn't receive an instruction to do so

  • 155 Views
Sounds great idea, which will give a space to clear our learning doubts.
AV_1
Cadet
Cadet
  • 146 Views
Description: Lab Hours
Hello, is there a way for me to check how many lab hours I’ve used? I remember using it for less than 30 minutes, but the console shows that it was stopped 2 hours ago. As a result, I can’t see details about how many hours I have left. Can you help with this? I also checked this thread https://learn.redhat.com/t5/DO316-Managing-Virtual-Machines/lab-hours/m-p/48859#M173, but I couldn’t find these numbers in my subscription.
cschunke
Community Manager
Community Manager
  • 458 Views

The number of hours used on your labs can be found in a few different places:

  1. On your Reports page. This will have a tab for "Lab Acrtivity" and list each lab and the number oif hours used.
  2. On the Dashboard. This will have a list of all labs that were created, and how many hours spent on each
  3. From a downloaded report. From either link above, there will be an option to download a TSV report. This report will list the courses where the labs were created, and include the number of hours used. 

Please note, that depending on your subscription type, you access to each of the above may be limited. 

Andy5
Cadet
Cadet
  • 64 Views
am having a technical issue with the lab "network-services" from Ch 3 where I can log into the project but am unable to start the lab as it starts to go through the checklist and fails at "Checking CatalogSource" and states "the ansible playbook failed execution - Cannt continue starting lab". The log is as follows:
```Traceback (most recent call last):
File "/home/student/.venv/labs/lib/python3.9/site-packages/labs/lab.py", line 352, in start
grading.prestart()
File "/home/student/.venv/labs/lib/python3.9/site-packages/labs/grading.py", line 25, in prestart
self.start()
File "/home/student/.venv/labs/lib/python3.9/site-packages/do316/network-services.py", line 225, in start
userinterface.Console(items).run_items(action="Starting")
File "/home/student/.venv/labs/lib/python3.9/site-packages/labs/common/userinterface.py", line 120, in run_items
raise LabError(msg)
labs.laberrors.LabError: The 'Checking CatalogSource' fatal step has failed
```
Andy5
Cadet
Cadet
  • 64 Views
I will destroy the lab and recreate - hopefully that solves it
  • 61 Views
I had the same issue few days ago, please connect to the utility machine via ssh lab@utility. Inside the utility machine, run :
oc login -u admin -p ********* https://api_server_url:6443
Once connected successfully, exit the utility machine and come back to the workstation machine. Finally, run : lab start lab_name
Hope it is helpful!
Join the discussion
You must log in to join this conversation.