- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 1,893 Views
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 1,717 Views
@Soumya_Gupta I checked the same in my lab , DO378 ch02s04 - could not replicate the error :
I suggest you to recheck / reverify the earlier steps or redo this whole exercise again.
If you still face this issue, I suggest you to raise a support case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 1,365 Views
Can you confirm you ran the "lab start XXX" command for that lab and it completed successfully. Normally, the command will setup the container registry, credentials, and ensure the image is available. You're getting an "unauthorized" based on the screenshot so I suspect that the registry isn't setup with the image and the correct permissions. This is a common error and behavior I've seen in the past when delivering courses as sometimes there is a timeout on the "Start" script and even if students do remember to run it, they don't pay attention and notice that there was a failure in the outtput
https://rhtapps.redhat.com/verify?certId=111-134-086
SENIOR TECHNICAL INSTRUCTOR / CERTIFIED INSTRUCTOR AND EXAMINER
Red Hat Certification + Training
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 1,734 Views
@Soumya_Gupta where are you trying this ? in this course ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 1,732 Views
Yes in this course. In one of the steps for this module it is mentioned to create a container which is basically using quarkus jib extension.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 1,731 Views
@Soumya_Gupta Please let me know the lab exercise name or chapter / section number so that I can take a look.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 1,730 Views
Guided Exercise: Developing REST based Microservices
Step 6.1 and 6.2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 1,726 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 1,718 Views
@Soumya_Gupta I checked the same in my lab , DO378 ch02s04 - could not replicate the error :
I suggest you to recheck / reverify the earlier steps or redo this whole exercise again.
If you still face this issue, I suggest you to raise a support case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 1,600 Views
Hi Chetan,
Thanks for your prompt response .. I tried it again but still the same error .. Can we please connect over a call before raising a support ticket .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 1,366 Views
Can you confirm you ran the "lab start XXX" command for that lab and it completed successfully. Normally, the command will setup the container registry, credentials, and ensure the image is available. You're getting an "unauthorized" based on the screenshot so I suspect that the registry isn't setup with the image and the correct permissions. This is a common error and behavior I've seen in the past when delivering courses as sometimes there is a timeout on the "Start" script and even if students do remember to run it, they don't pay attention and notice that there was a failure in the outtput
https://rhtapps.redhat.com/verify?certId=111-134-086
SENIOR TECHNICAL INSTRUCTOR / CERTIFIED INSTRUCTOR AND EXAMINER
Red Hat Certification + Training
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 1,343 Views
Can confirm, this also happens to me.
I picked up at ch02s04 this morning and had also trouble executing:
lab start develop-rest
Yesterday i had no issues running the lab start / lab finish commands, today, they all fail with similiar errors:
Could not find modules for course do378
CRITICAL:root:Traceback (most recent call last):
File "/home/student/.venv/labs/lib/python3.9/site-packages/labs/labload.py", line 26, in loadcache
module = importlib.import_module(course)
File "/usr/lib64/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
File "<frozen importlib._bootstrap>", line 984, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'do378'
Could not find modules for course do378
CRITICAL:root:Traceback (most recent call last):
File "/home/student/.venv/labs/lib/python3.9/site-packages/labs/labload.py", line 26, in loadcache
module = importlib.import_module(course)
File "/usr/lib64/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
File "<frozen importlib._bootstrap>", line 984, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'do378'
ERROR:root:Lab script has failed due to a LabError: Script develop-rest not in course library do378
Traceback (most recent call last):
File "/home/student/.venv/labs/lib/python3.9/site-packages/labs/lab.py", line 235, in start
grading = labload.import_grading_library(config, script)
File "/home/student/.venv/labs/lib/python3.9/site-packages/labs/labload.py", line 130, in import_grading_library
raise LabError("Script %s not in course library %s" % (name, course))
labs.laberrors.LabError: Script develop-rest not in course library do378
An error has occurred. For more details, run: lab logs develop-rest
Running
lab logs develop-rest
yields empty output.