Currently, a validation error is thrown if we find any PCI device
records which have not populated the parent_addr column on a nova
upgrade. However, the only PCI records for which a parent_addr
makes sense for are those with a device type of 'type-VF' (ie. an
SRIOV virtual function). PCI records with a device type of 'type-PF'
or 'type-PCI' will not have a parent_addr. If any of those records
are present on upgrade, the validation will fail.
This change checks that the device type of the PCI record is
'type-VF' when making sure the parent_addr has been correctly
populated
Closes-Bug: #1680918
Change-Id: Ia7e773674a4976fc03deee3f08a6ddb45568ec11
(cherry picked from commit 7f3f0ef1fbb51f6f17d2c13840e0f98d17fa9093)
(cherry picked from commit c23c5e9f747e7127497dfd77ca0b33df2be74a2d)
Reviewed: https:/ /review. openstack. org/458668 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=ad12fa65f5c c06bdee52be49b7 370d703855d618
Committed: https:/
Submitter: Jenkins
Branch: stable/newton
commit ad12fa65f5cc06b dee52be49b7370d 703855d618
Author: Steven Webster <email address hidden>
Date: Wed Apr 5 09:05:07 2017 -0400
Fix mitaka online migration for PCI devices
Currently, a validation error is thrown if we find any PCI device
records which have not populated the parent_addr column on a nova
upgrade. However, the only PCI records for which a parent_addr
makes sense for are those with a device type of 'type-VF' (ie. an
SRIOV virtual function). PCI records with a device type of 'type-PF'
or 'type-PCI' will not have a parent_addr. If any of those records
are present on upgrade, the validation will fail.
This change checks that the device type of the PCI record is
'type-VF' when making sure the parent_addr has been correctly
populated
Closes-Bug: #1680918 fc03deee3f08a6d db45568ec11 f17d2c13840e0f9 8d17fa9093) 7497dfd77ca0b33 df2be74a2d)
Change-Id: Ia7e773674a4976
(cherry picked from commit 7f3f0ef1fbb51f6
(cherry picked from commit c23c5e9f747e712