yahoo-eng-team team mailing list archive

[Balazs Gibizer <1983753@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Nova does not consider the pci_alias from the new flavor extra_specs
during the scheduling of the resize. The new pci_request only applied by
the resource_tracker during the move claim[1].

This leads to a behavior where during the scheduling of the resize nova
selects the target host according to the old flavor's pci_request but
then at the selected host it will allocate PCI devices properly based on
the new flavor.

[1]
https://github.com/openstack/nova/blob/adeea3d5e7d7337d2817dd5c46334c76c05995ef/nova/compute/resource_tracker.py#L287-L299

** Affects: nova
     Importance: Undecided
     Assignee: Balazs Gibizer (balazs-gibizer)
         Status: New


** Tags: pci

** Tags added: pci

** Changed in: nova
     Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)

-- 
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/1983753

Title:
  Resize with changing pci alias schedules accoring to the old flavor

Status in OpenStack Compute (nova):
  New

Bug description:
  Nova does not consider the pci_alias from the new flavor extra_specs
  during the scheduling of the resize. The new pci_request only applied
  by the resource_tracker during the move claim[1].

  This leads to a behavior where during the scheduling of the resize
  nova selects the target host according to the old flavor's pci_request
  but then at the selected host it will allocate PCI devices properly
  based on the new flavor.

  [1]
  https://github.com/openstack/nova/blob/adeea3d5e7d7337d2817dd5c46334c76c05995ef/nova/compute/resource_tracker.py#L287-L299

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