Public bug reported:
Changes in PCI device configuration is not reflected in the database
(pci_stats). After nova reboot, pci_stats still hold stale data.
Steps to reproduce:
1. Configure SR-IOV on an interface and edit
nova.conf/pci_passthrough_whitelist accordingly.
2. Start nova on the compute.
3. Remove the SR-IOV interface and it's configuration in nova.conf.
4. Restart nova on the compute.
5. Validate that pci_stats still hold the PCI device information by looking at
the SQL database.
This behavior cause the scheduler to still try to schedule an instance
on the compute that had PCI configured even since no PCI device are
availalble.
** 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/1487451
Title:
Stale pci_stats in the DB after PCI reconfiguration
Status in OpenStack Compute (nova):
New
Bug description:
Changes in PCI device configuration is not reflected in the database
(pci_stats). After nova reboot, pci_stats still hold stale data.
Steps to reproduce:
1. Configure SR-IOV on an interface and edit
nova.conf/pci_passthrough_whitelist accordingly.
2. Start nova on the compute.
3. Remove the SR-IOV interface and it's configuration in nova.conf.
4. Restart nova on the compute.
5. Validate that pci_stats still hold the PCI device information by looking
at the SQL database.
This behavior cause the scheduler to still try to schedule an instance
on the compute that had PCI configured even since no PCI device are
availalble.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1487451/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
