New Lab Machine Reset Behavior

Latest response

Hello community members,

Last week we implemented a change in how we, on the back-end, execute lab machine
resets.

You'll notice that now:
After 10-20 seconds, the state of the reset machine switches to "UPDATING"
and
Reset machines retain their original names (no more @_resetXX extensions)

The nitty-gritty:
Prior to last week, we employed machine image based resets. Meaning that in
your deployed lab application, we'd delete your target system, then insert a new
machine from our image library to replace it. We added the @_resetXX nomenclature
so that it would be easier to identify the old vs. new machine in your lab environment.

In the new method, we turn off the machine, detatch it's disk image overlay, and attach
a new overlay in it's place.

As a result, the "machine" is kept the same, but it's disk is reverted to it's initial state.
Because we're keeping the same machine, we keep the same machine name.

In my testing over the last few weeks, I've noticed significantly improved reset times.

-Scott

Responses

Not sure that 'reset' is working properly.... working through RH436v7, and unable to reset any of my lab VMs. The reset link asks if I am sure, and then nothing happens. The only way I can 'reset' my lab environment at the moment is to destroy the whole lab and then reprovision.... all vm's....

Sunday our cloud provider made a change to our account which affected the individual machine reset operation.

We've been working with them to resolve the issue, but until it's resolved, the work around would be to delete and reprovision the entire lab, though that is not a solution in some classes where individual machines are re-used for different activities and others need to be kept with their built-through-sequential-lab-exercises configuration. Students will have to use their best judgement on whether a lab reprovision or waiting while we resolve the issue is the best course of action based on their course.

-STM

It seems like its fixed now?

Yes, we resolved the issue with the Cloud provider a day or so after my update. I had put in-product notifications up about the issue, along with updating those messages, and neglected to close out the thread here.

-STM

Close

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