You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An existing environment previously released was expanded with additional hosts. I was expecting that the subsequent validation would only encompass the expansion hosts, and not the previous hosts. However, after adding expansion hosts to an existing environment, I noticed the following in the validation log (after the expansion hosts were successfully provisioned):
Validating cloud38
The following hosts appear to be down or with no ssh connection:
e26-h17-000-r640.example.com
e30-h01-000-r640.example.com
e30-h02-000-r640.example.com
e30-h03-000-r640.example.com
e30-h05-000-r640.example.com
e30-h07-000-r640.example.com
e30-h09-000-r640.example.com
e30-h10-000-r640.example.com
e30-h11-000-r640.example.com
e30-h13-000-r640.example.com
e30-h14-000-r640.example.com
e30-h17-000-r640.example.com
e30-h18-000-r640.example.com
e30-h19-000-r640.example.com
e30-h21-000-r640.example.com
Quads assignments validation executed.
Note that the hosts shown in the validation log were not the expansion hosts, but rather the existing hosts that had already passed validation when the environment first went out. Furthermore, the hosts (that start with e30) had their switch configs modified (intentionally) to be on the same network as a different environment, using the modify_switch_conf.py command. This modified network membership we reverted when the environment expansion decided to touch the pre-existing hosts.
It's not clear if the hosts were properly marked as validated from the previous release.
Version: quads-2.1.6-20250210.noarch
An existing environment previously released was expanded with additional hosts. I was expecting that the subsequent validation would only encompass the expansion hosts, and not the previous hosts. However, after adding expansion hosts to an existing environment, I noticed the following in the validation log (after the expansion hosts were successfully provisioned):
Note that the hosts shown in the validation log were not the expansion hosts, but rather the existing hosts that had already passed validation when the environment first went out. Furthermore, the hosts (that start with e30) had their switch configs modified (intentionally) to be on the same network as a different environment, using the
modify_switch_conf.py
command. This modified network membership we reverted when the environment expansion decided to touch the pre-existing hosts.It's not clear if the hosts were properly marked as validated from the previous release.
The docs also indicate that I can skip specific hosts during validation by running the following as per: https://github.com/redhat-performance/quads/tree/latest?tab=readme-ov-file#skipping-past-network-and-systems-validation-per-host
The text was updated successfully, but these errors were encountered: