yahoo-eng-team team mailing list archive

[Jing Zhang Nokia <1765530@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

This happens with VM with either tap (vif type ovs), or SRIOV (vif type
hw_veb), or vhostuser (vif type vhostuser) ports in master (Queens)
after nova/virt/libvirt/driver.py code change per
https://git.openstack.org/cgit/openstack/nova/commit/?id=aaf37a26d6caa124f0cc6c3fe21bfdf58ccb8517
per https://bugs.launchpad.net/neutron/+bug/1744361.

This is because the above nova change only un-blocks VM from waiting
network-vif-plugged event for vif type "bridge". The approach taken is
questionable since it is error prone (has to unblock vif type one by
one) and not future safe (new vif type can be added).

We propose either unblocks VM from waiting for network-if-plugged event
for hard reboot completely, this is what we are doing now locally, or
fix the root cause of missing network-if-plugged events in the host
reboot scenario.

For comparison, we have checked Newton, we see exactly the same VM start
up events in Newton, only network-vif-plugged event arrives as VM
expects so VM is able to reboot successfully.


Please review and fix the issue.

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1765530

Title:
  VM failed to reboot after compute host reboot in Queens

Status in neutron:
  New

Bug description:
  This happens with VM with either tap (vif type ovs), or SRIOV (vif
  type hw_veb), or vhostuser (vif type vhostuser) ports in master
  (Queens) after nova/virt/libvirt/driver.py code change per
  https://git.openstack.org/cgit/openstack/nova/commit/?id=aaf37a26d6caa124f0cc6c3fe21bfdf58ccb8517
  per https://bugs.launchpad.net/neutron/+bug/1744361.

  This is because the above nova change only un-blocks VM from waiting
  network-vif-plugged event for vif type "bridge". The approach taken is
  questionable since it is error prone (has to unblock vif type one by
  one) and not future safe (new vif type can be added).

  We propose either unblocks VM from waiting for network-if-plugged
  event for hard reboot completely, this is what we are doing now
  locally, or fix the root cause of missing network-if-plugged events in
  the host reboot scenario.

  For comparison, we have checked Newton, we see exactly the same VM
  start up events in Newton, only network-vif-plugged event arrives as
  VM expects so VM is able to reboot successfully.

  
  Please review and fix the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1765530/+subscriptions