RH413 Lab not working

Latest response

Hi,

The VMs provisioned for RH413 are not subscribed to the Red Hat repo and the labs cannot access instruction.example.com. Running you repolist or yum updateinfo failed. The vms also does not have access to the internet.

Can someone help please.

Responses

Hi Lateef Onifade,

Sorry you're having trouble with your lab. You might not be aware of this, your Red Hat Learning Subscription is a supported product. I recommend you submit a case with Red Hat. Community support may not be the best avenue to get your issue resolved.

  • Go to this link: https://access.redhat.com/support/cases/, which is at the top of this page too, named SUPPORT CASES.
  • In the Product drop down, select: Red Hat Online Learning (NOTE: You will need to scroll down through a list in the drop-down menu)
  • Important, in the Product Version drop down, select the largest number (as I type this, it is 1.0, but that may change over time) NOTE: the "Submit" button won't activate until this is selected.
  • In the Case Type drop down, select: Other
  • In the Problem Statement block, enter something concise, the course number, and a small description.
  • In the Case Description block, enter the specifics.

The other blocks are straightforward enough. When I've submitted a ticket for Red Hat Online Learning, I make it a low priority, it certainly is not production. One of the course administrators does on occasion check the forum, but you ought to submit a ticket for this issue since this is supported.

The Training Principal Product Manager also highly recommends submitting a case for this, as the experiences of one customer in resolution may not necessarily work with another (paraphrasing) see this link, it leads to his comments

I had the same problem with the RH413 lab... You will have three VM's - Server, Desktop and Classroom. Check the status of the 'Classroom' machine - that is instructor.example.com. In my case, that machine had not successfully booted when the lab was started, the result being that the other two VM's had no IP address, as 'classroom' is the DNS, DHCP and Repo server for the environment. In my case simply rebooting the 'classroom' machine fixed all the problems as it booted successfully on the second attempt.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.