Please fill in the following information:

Issue description
AD248 Issues

• Classroom VM has incorrect MTU for ETH0. It has JUMBOFrames enabled with MTU of 8942 and not the MTU 1500. This will cause problems in the physical environment. I had made Ansible checks for this, but I don't think it is in the automated pipeline.
• Workstation VM graphical console never loads ... VM doesn't truly finish booting
• Issues complaining about Podman can't start classroom_webapp (Don't think it should try to start for ILT builds)
• Issues where workstation is attempting to access a CD-ROM drive most likely (/dev/sr0) issues stating it "Can't open block device"

• Lab framework is 4.17.1 but nothing seems to be working. Crashes with lab start <tab> <tab> as it gives Python errors that are critical with traceback to loadlab.py.
• My guess here we don't have the GLS core Dynolabs framework and there doesn't seem to be a Dynolabs package and library for AD248. It would appear that it has the generic course library of rht-labs-gl006 which I believe is the dummy (starter) workstation package

AD248 or RHCI Foundation Issues:

• DNS on Foundation0 and FoundationX machines doesn't resolve any of the hosted VMs. I believe there is a Foundation script that does this based on some of the network pieces and it is an RC script. However, I also noticed that the Classroom VM doesn't have a DNS server on it from Podman (not sure if it is needed for AD248).
• Can't SSH from Foundation0 to Classroom as root. (All other courses, the SSH key allows directly SSHing as root - this causes issues with my playbooks - it is fixable, but need to know if this is intended).
• the reason the RHT-External script isn’t working is the SSH to the classroom using root doesn’t work because the InstructorKey is missing from authorized keys. There are no keys for the root user on the Classroom machine.
   
   

Steps to reproduce:

Workaround:

Expected result: