yahoo-eng-team team mailing list archive

[Claudiu Belu <cbelu@xxxxxxxxxxxxxxxxxxxxxx>]

** Also affects: compute-hyperv
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1473291

Title:
  nova compute on hyperv don't wait for vif plugged event from neutron

Status in compute-hyperv:
  New
Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  1. Exact version of Nova/OpenStack you are running: 
  Juno/stable

  2. Reproduce steps:

  * Launch a VM on a Hyper-V cloud.
  * Note the boot time of the Virtual Machine in nova-compute.log.
  * Note the port up status time in neutron DB for the port of the VM.

  The boot time of the Virtual machine is earlier than the port UP
  status, which should not be the case.

  Expected result:
  * The boot time of the Virtual Machine should be later than port UP status.
  * All port rules are applied before the VM is booted and presented to the user.

  Actual result:
  * VM boots before the port rules are applied by neutron and it results in VM not getting IP, missing rules to communicate etc.

  4. Description
  When the port binding is complete, neutron uses notifier to notify the port UP event to Nova, so that Nova could power ON or resume the VM instance. On Nova compute for hyper-v, Nova doesn't wait for the Port Up event from neutron and boots the instance immediately once the disk preparation is done. 
  This causes VM instances to boot without proper security rules and hence would result in VMs not getting IP or connectivity as desired by the user. To prevent this, Nova compute should wait for the vif plugged event from neutron and then do power ON operation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compute-hyperv/+bug/1473291/+subscriptions