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
The playbook designed to swap a virtual machine (VM) successfully completes all tasks without errors. However, after the swap is performed, the new VM is unable to establish network connectivity. This prevents any external communication with the server, making it inaccessible.
Actual behavior
Error messages
Include any error messages from STDOUT, STDERR, log files, etc., that you did not include under 'Actual behavior' above.
Steps to replicate
Prepare Environment:
Have a running VM (VM-A) with a working network connection.
run playbook and wait for replacement VM (VM-A-new) with a working network connection.
Expected Behavior:
The VM swap playbook should result in a fully functional VM (VM-A-new) that has network connectivity. I should be able to connect to the VM via SSH, ping, and other network services as configured.
Actual Behavior:
The playbook reports success, but the swapped VM (VM-B) has no network connectivity. Attempts to connect via SSH, ping, or other protocols fail. The VM is essentially isolated from the network.
Impact of this bug
Ops have to manually log in at the console
and run
sudo dhclient -v
then create this systemd unit file
[Unit]Description=DHCP Client for %i
After=network.target
[Service]ExecStart=/sbin/dhclient -v %i
Restart=always
[Install]WantedBy=multi-user.target
Relevant links and code snippets, if applicable
Implementation notes, if any
The text was updated successfully, but these errors were encountered:
Expected behavior
The playbook designed to swap a virtual machine (VM) successfully completes all tasks without errors. However, after the swap is performed, the new VM is unable to establish network connectivity. This prevents any external communication with the server, making it inaccessible.
Actual behavior
Error messages
Include any error messages from STDOUT, STDERR, log files, etc., that you did not include under 'Actual behavior' above.
Steps to replicate
Prepare Environment:
Expected Behavior:
The VM swap playbook should result in a fully functional VM (VM-A-new) that has network connectivity. I should be able to connect to the VM via SSH, ping, and other network services as configured.
Actual Behavior:
The playbook reports success, but the swapped VM (VM-B) has no network connectivity. Attempts to connect via SSH, ping, or other protocols fail. The VM is essentially isolated from the network.
Impact of this bug
Ops have to manually log in at the console
and run
then create this systemd unit file
Relevant links and code snippets, if applicable
Implementation notes, if any
The text was updated successfully, but these errors were encountered: