Please fill in the following information:

Issue description

The common Ansible playbook used in all systems to check connectivity does not work as designed or verify what it thinks it should. Currently, if DNS is messed up on the systems and it can't resolv, it will sit and wait indefinitely for a connection to be made.

Steps to reproduce:

Can't easily and reliably be reproduced in the ROL/VT environment as the systems will sometimes have an IP address and hostname for IPv6 so it hides and masks the issue. One way to test is specifically disable IPv6 on the host and then run the "lab start dns-tshooting" command, allow it to connect and mess up DNS. Then attempt to either run lab start again or the lab finish, which should finish DNS, but it will hang indefinitely. 

Before running lab finish or lab start a second time, SSH to serverA from workstation and attempt to ping serverA on itself. If it resolves with the IPv6, you didn't disable IPv6 correctly, if it resolves with the 172.25.250.10 address, the /etc/resolv.conf isn't messed up. However, if it doesn't resolv, feel free to go back to workstation and attempt any lab command and it won't work.

The logic in the playbook and steps to see if servers are alive is incorrect and this will prevent any future labs or exercises from working with the scripts.

Workaround:

NONE (other than don't use the script) ... a secondary work around would be modifying all lab scripts and removing the check to see if a server is alive. Another thing that could be done is accessing each individual server and checking /etc/resolv.conf and manually fixing. None of these are good work-arounds.

Expected result:

The scripts should work and only check to ensure workstation can contact the other servers before it continues running the playbooks and configuring the systems.