yahoo-eng-team team mailing list archive

[Hamdy Khader <1822801@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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_host_id=overcloud-controller-0.localdomain


[1] https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L7191


Nova version:
()[root@overcloud-controller-0 /]# rpm -qa | grep nova
puppet-nova-14.4.1-0.20190322112825.740f45a.el7.noarch
python2-nova-19.0.0-0.20190322140639.d7c8924.el7.noarch
python2-novajoin-1.1.2-0.20190322123935.e8b18c4.el7.noarch
openstack-nova-compute-19.0.0-0.20190322140639.d7c8924.el7.noarch
python2-novaclient-13.0.0-0.20190311121537.62bf880.el7.noarch
openstack-nova-common-19.0.0-0.20190322140639.d7c8924.el7.noarch

** Affects: nova
     Importance: Undecided
     Assignee: Hamdy Khader (hamdyk)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Hamdy Khader (hamdyk)

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

Title:
  Baremetal port's host_id get updated during instance restart

Status in OpenStack Compute (nova):
  New

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_host_id=overcloud-controller-0.localdomain

  
  [1] https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L7191

  
  Nova version:
  ()[root@overcloud-controller-0 /]# rpm -qa | grep nova
  puppet-nova-14.4.1-0.20190322112825.740f45a.el7.noarch
  python2-nova-19.0.0-0.20190322140639.d7c8924.el7.noarch
  python2-novajoin-1.1.2-0.20190322123935.e8b18c4.el7.noarch
  openstack-nova-compute-19.0.0-0.20190322140639.d7c8924.el7.noarch
  python2-novaclient-13.0.0-0.20190311121537.62bf880.el7.noarch
  openstack-nova-common-19.0.0-0.20190322140639.d7c8924.el7.noarch

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