Soumya_Gupta
Mission Specialist
Mission Specialist
  • 1,017 Views

Getting 403 error in Ch02s04 lab step 6.1 & 6.3

Jump to solution

I am unable to create a container image due to 401 Unauthorized access while connecting to https://registry.ocp4.example.com:8443

Labels (7)
2 Solutions

Accepted Solutions
Chetan_Tiwary_
Community Manager
Community Manager
  • 900 Views

@Soumya_Gupta I checked the same in my lab , DO378 ch02s04 - could not replicate the error :

Chetan_Tiwary__0-1720633102451.png

 

Chetan_Tiwary__1-1720633111173.png

Chetan_Tiwary__2-1720633320628.png

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. 

View solution in original post

Travis
Moderator
Moderator
  • 548 Views

@Soumya_Gupta -

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

Travis Michette, RHCA XIII
https://rhtapps.redhat.com/verify?certId=111-134-086
SENIOR TECHNICAL INSTRUCTOR / CERTIFIED INSTRUCTOR AND EXAMINER
Red Hat Certification + Training

View solution in original post

10 Replies
Chetan_Tiwary_
Community Manager
Community Manager
  • 917 Views

@Soumya_Gupta where are you trying this ? in this course ? 

0 Kudos
Soumya_Gupta
Mission Specialist
Mission Specialist
  • 915 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.

Chetan_Tiwary_
Community Manager
Community Manager
  • 914 Views

@Soumya_Gupta Please let me know the lab exercise name or chapter / section number so that I can take a look.

0 Kudos
Soumya_Gupta
Mission Specialist
Mission Specialist
  • 913 Views

Guided Exercise: Developing REST based Microservices

Step 6.1 and 6.2

Soumya_Gupta
Mission Specialist
Mission Specialist
  • 909 Views

Screenshot 2024-07-10 at 10.22.30 PM.png

Chetan_Tiwary_
Community Manager
Community Manager
  • 901 Views

@Soumya_Gupta I checked the same in my lab , DO378 ch02s04 - could not replicate the error :

Chetan_Tiwary__0-1720633102451.png

 

Chetan_Tiwary__1-1720633111173.png

Chetan_Tiwary__2-1720633320628.png

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. 

Soumya_Gupta
Mission Specialist
Mission Specialist
  • 783 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 . 

 

0 Kudos
Travis
Moderator
Moderator
  • 549 Views

@Soumya_Gupta -

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

Travis Michette, RHCA XIII
https://rhtapps.redhat.com/verify?certId=111-134-086
SENIOR TECHNICAL INSTRUCTOR / CERTIFIED INSTRUCTOR AND EXAMINER
Red Hat Certification + Training
DWinter
Cadet
Cadet
  • 526 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.

Join the discussion
You must log in to join this conversation.