Windows contrail installer gets stuck in reboot windows VM step
Bug #1803012 reported by
Lajapathy Madhusudhanan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
New
|
Undecided
|
Michał Kostrzewa |
Bug Description
sudo -H ansible-playbook -i inventory/ playbooks/
The above playbook gets stuck in the following step,
TASK [instance : reboot the system] *******
Network connectivity gets lost in the Windows compute nodes. If we manually restart the network interface in the windows VM, playbook resumes.
Changed in juniperopenstack: | |
assignee: | nobody → Michał Kostrzewa (mkostrzewa) |
information type: | Proprietary → Public |
To post a comment you must log in.
Similar to https:/ /bugs.launchpad .net/juniperope nstack/ +bug/1803537, this issue was probably caused by older version of virtio NIC drivers for Windows. Update of virtio-win drivers to a 0.1.141 version, newest at the moment, should resolve the issue.
However, this bug occurred in the different environment. Contrail Windows compute node had one virtual NIC, as opposed to an environment from https:/ /bugs.launchpad .net/juniperope nstack/ +bug/1803537 where it had two NICs.
Need to verify it on the single interface setup, with newest virtio-win driver installed.