Unable to stop DO370 lab to conserve lab hours

[donaldsebleung]

About 15 minutes ago I've clicked the "Stop" button on the DO370 lab to conserve my lab hours but it's been loading for at least 15 minutes and all VMs are still shown as "Active". Furthermore, the "Action > Power Off" action on each individual VM is unresponsive and all VMs remain in "Running" status.

Stopping the lab or powering off each VM has no effect

Checking the Red Hat Status page at https://status.redhat.com/ indicates that the labs at access.redhat.com are experiencing a service outage but I have not received a notification email from Red Hat so far acknowledging the outage. Note that I have subscribed to the Red Hat Status page.

access.redhat.com Labs service outage

status.redhat.com "No incidents reported today"

Another issue I encountered right before discovering this outage - I was attempting the comprehensive review at the end of the DO370 course and in the midst of reconfiguring and restarting some workloads, I got an ImagePullBackOff for workloads using the image "registry.ocp4.example.com:8443/redhattraining/image-tool:latest" stating that authentication is required. I tried pulling the image locally with Podman and confirmed the authentication error. I tried the registry login credentials "developer/developer" with the "podman login" command which errored out with invalid username/password. Surprisingly, visiting https://registry.ocp4.example.com:8443/ in a web browser and entering the identical set of credentials succeeded as expected and I was logged in to the registry. Since I don't see how troubleshooting the external Quay registry is part of the DO370 course syllabus, could this issue be related to the lab environment outage as well?

P.S. I've used 106/400 lab hours with my RHLS Standard thus far; hopefully the VMs remaining active due to the lab environment outage will not cost me additional lab hours.

RHLS Standard 106/400 lab hours used

[Ksharif]

I am experiancing the same issue, Almost an hour now, lab stuck in building stage and consuming lab hours.

[Simon_]

My lab is also stuck in build for +2 hours now. Very disappointing.

[TudorRaduta]

@Simon_ @Ksharif thanks for bringing this up in the Learning Community. The best next step for anyone facing these issues is to raise a support ticket directly in the Learning portal, if you haven’t already. That way, the team can look into it and share the right options to help you move forward.

[Chetan_Tiwary_ · Accepted solution]

@donaldsebleung Regarding your issue - I will recommend you to raise a support case with the details you mentioned here which could be better handled and answered by our backend support team. Yes, we had an outage during the weekend and it was resolved yesterday - your labs should be workinig fine now.