RH413 (Hardening) - Classroom VM broken

Latest response

Hello,

I have been trying to use the lab in the course RH413 (Red Hat Server Hardening) and I have been facing network issues (no network at all), which leaves the lab completely useless. Even deleting and regenerating the lab keeps giving me problems. It seems that the Classroom VM is broken and shows udev errors because of the LVM (/devices/virtual/block/dm-X).

I am attaching a screnshot for reference.

.

EC
Log in to join the conversation

Responses

R. Hinton.'s picture Guru 10133 points
2 March 2018 1:20 AM

Hi Eloi Carbo,

Sorry you're having trouble with your lab. That looks really abnormal and you certainly can submit a case. It seems likely that your underlying (virtual lab) system might be experiencing an issue that needs to be fixed by Red Hat ---and --- 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. That certainly looks abnormal and something that Red Hat itself needs to fix. so..

  • 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 Also examine the Red Hat course updates page at https://access.redhat.com/discussions/3344631. for up to the date info they post.

Amin Busaboul's picture Active Contributor 112 points
2 March 2018 9:39 PM

I faced the same issue while taking the course. Support recommended that I start the classroom VM before others, wait until it is completely up (Which takes 10-15mins sometimes) before starting other machines.

EC Newbie 17 points
5 March 2018 9:45 AM

Hello both,

I have opened a case as R. Hinton suggested (thanks for your help!) and I got response from RHEL. They have confirmed the issue and provided a workaround while they fix the VMs.

To avoid that big chunck of wasted time that Amin Busaboul mentions, you can click on the "Ctrl+Alt+Del" button and the system will reboot at once. After that reboot, the system will be "cleared" of LVM issues. I have not tested what is quicker though.

Best regards,

Scott McBrien's picture Red Hat Pro 650 points
5 March 2018 8:37 PM

I found this a couple of weeks ago, apparently there was a change in how devices are being presented to the machine prior to it's booting. I'm working with the cloud provider to either resolve it on their end, or if they are unable to do so, will then work on getting it resolved with some sort of update to the machine (which isn't my preference as anytime you make a change a QA'ed environment you risk injecting something that causes other problems).

Apparently, if you reboot the machine, by hitting the -- button on the console interface, it'll come up cleanly on it's reboot.

-STM

Close

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