yahoo-eng-team team mailing list archive

["Jesse J. Cook" <jesse.cook@xxxxxxxxxxxxx>]

Public bug reported:

Observed nova pass the correct device number during vbd creation to
xenserver, but the nova mapping created in the database was for the
wrong device.

A bdm for swap, based on the flavor, is created on
https://github.com/openstack/nova/blob/master/nova/compute/api.py#L725,
but the swap is actually created on
https://github.com/openstack/nova/blob/master/nova/virt/xenapi/vmops.py#L746,
again based on flavor, but with no regard for the previously created bdm
for swap.

Perhaps we should implement default_device_names_for_instance() in xen
driver (as referenced on
https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L1631).

** Affects: nova
     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/1482403

Title:
  bdm for swap created with no regard for previous

Status in OpenStack Compute (nova):
  New

Bug description:
  Observed nova pass the correct device number during vbd creation to
  xenserver, but the nova mapping created in the database was for the
  wrong device.

  A bdm for swap, based on the flavor, is created on
  https://github.com/openstack/nova/blob/master/nova/compute/api.py#L725,
  but the swap is actually created on
  https://github.com/openstack/nova/blob/master/nova/virt/xenapi/vmops.py#L746,
  again based on flavor, but with no regard for the previously created
  bdm for swap.

  Perhaps we should implement default_device_names_for_instance() in xen
  driver (as referenced on
  https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L1631).

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