Baremetal port's host_id get updated during instance restart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Hamdy Khader | ||
Stein |
Fix Committed
|
High
|
Matt Riedemann |
Bug Description
In case of baremetal overcloud, the instance ports gets updated during instance reboot[1] to change host_id
to be the nova compute host_id.
This way baremetal ports' host_id will be changed to indicate the nova host_id instead of ironic node uuid.
In case of normal instance or even baremetal instance it wouldn't be a problem but in case of SmartNIC
baremetal instance the port's host_id is important to communicate with the relevant Neutron agent running on the SmartNIC as the port's host_id contains the SmartNIC host name.
Reproduce:
- deploy baremetal overcloud
- create baremetal instance
- after creation complete, check port details and notice binding_
[1] https:/
Nova version:
()[root@
puppet-
python2-
python2-
openstack-
python2-
openstack-
Changed in nova: | |
assignee: | nobody → Hamdy Khader (hamdyk) |
Changed in nova: | |
assignee: | Hamdy Khader (hamdyk) → Adrian Chiris (adrian.chiris) |
Changed in nova: | |
assignee: | Adrian Chiris (adrian.chiris) → Hamdy Khader (hamdyk) |
Fix proposed to branch: master /review. openstack. org/649345
Review: https:/