URL:
Reporter RHNID:
Section: -
Language: en-US (English)||||||||
Workaround:

Description: Reported by ROLE student Patrick Herring (patrick.herring@dorsett.com.au):
against the lab network grade script used in RH199 Chapter 10 / RH124 Chapter 11 end-of-chapter lab "Lab: Managing Red Hat Enterprise Linux Networking".

Ian and I believe we have uncovered a problem one of the labs in RH199.
Specifically lab network grade

When grading some work I had done on my DesktopX system it was saying I had failed to set the hostname correctly.
After messing around for a while I clicked show solution.
The solution which was

echo "10.0.X.1  private" >> /etc/hosts 

was identical to what I had already
specified. In my scenario my command would be

echo "10.0.13.1  private" >> /etc/hosts

So Ian and I investigated the grading script lab-network and found a potential issue on line 134.

The line reads

grep "10\.0\.[[:digit:]]\.1.*${hosts_name}" /etc/hosts &>/dev/null

We believe this is incorrect for anyone participating in the lab with a terminal number bigger than a single digit say 0-9.
My X value is 13.

So I considered maybe this bug had already been corrected and I may have had an older version of the grading script. I noticed in the lab script that if the grading script doesn't exist that it will download a new version of the script from a remote server.

Keeping this in mind I deleted my local copy of the script and ran the grading again. Same error here and it FAILED again. Checking the code on line 134 it was the same.

When we modified the code slightly to read

grep "10\.0\.[[:digit:]][[:digit:]]\.1.*${hosts_name}" /etc/hosts &>/dev/null

Which will now support X being a double digit I was able to achieve a PASS mark. While this fix isn't ideal if someone had a 3 digit value for X they would run into this problem. It highlights an issue that needs correcting on the grading scripts.

As we are unsure who to send this bug to at Redhat we thought you could forward it on for us to save other users this confusion.
I have attached screenshots of the original script and our slightly modified version. We are quite curious as to any feedback Redhat has on this bug.