Please fill in the following information:

Issue description

Step 3.1 This is a lot of text for a student to write by hand, so it might be worth creating it from the lab script as we've done with other files.

The other issue is that, even if I use copy/paste, vim tends to use autoindent (even when you unset it).  I used to be able to use \vi to ignore special features, but that no longer works.  When vim recognizes yaml, it will automatically indent and throw the indentation off.  Oh, I found it!  In vim, before you paste, run:
:set indentkeys=

That will remove all indentation triggers.

Step 4 Why has the ansibleHost IP address changed from the CR?  Is this build vs. run?  It seems really strange to me that we are having to change the IP addresses of the ansibleHost to get this to work.  This explains why I have having so many issues in this lecture.

Step 4.3 Why do we add custom-message to the top of the file?  Is this because it fails later on?  I think we made a point in the lecture that you should have custom services come at the end, so we should show that here.

Step 4.4 In all the previous lessons, we painstakenly went through dry-run/validate with every change, and here we just use oc apply.  It is a better practice to test/validate before applying, so we should add the --dry-run=server, --validate=true and oc diff to validate everything before we apply.  This will keep students doing the right thing.

Step 5 It seems like we go to the utility VM only because we want to log in to the compute nodes in step 6.  These commands all work from workstation, so I think you should remove step 5.1 (to login to utility) and do everything in this step from workstation.  If you want to log in to utility (I recommend just creating a simple entry in .ssh/config on workstation so you can ssh directly from workstation to compute nodes, as I've mentioned in previous bug reports), put that command in step 6.

Step 5.3 we show an oc create instead of the oc apply we show in the lecture material.  It does indeed new a new unique name to be created for each deployment.

I'll have to try this again, but in step 5 I realized that I had made a mistake and I forgot to change the IP addresses of the ansibleHosts.  I had already done a deploy, so I tried deleting the deployment and reusing the name.  I think it kept the status of the original name, even though I deleted and recreated it.  It currently shows a status of failed, even though the logs show the Ansible code completed successfully.  This may further prove that you need a unique name for each deployment.

In step 4.5 we show the status of the nodeset and in step 5.4 we show the status of the deployment (not started/in progress respectively).   We never follow up at the end to show that these are now working.  Is this because things break?  I still think we need a final step to show the status of both of these (even if they are broken).

Step 6 as in other bug reports, I think we should configure workstation to allow students to easily ssh to the compute nodes.  Then this becomes two substeps (instead of 6) and we remove step 7 entirely.

Step 8 as in other bug reports, remove `oc project default` everywhere.

Finish this states that there is an issue with the environment where you have to redeploy the entire lab environment (at a cost of 30 minutes or more to create an start a new environment).  Is anyone working on this? Is it still broken?  What does it look like?  Like I said, I think my Ansible code worked, but I'm not sure what the errors were that you were seeing.  I definitely had issues when I was running my lecture (I tried adding custom service and I tried removing a compute node), but I wasn't aware of the need to change the ansibleHost IP addresses.  I'll try it again to see if it works for me now.