[Bug 1839715] Re: masakari fails if hypervisor name does not match nova service name

Ryan Beisner 1839715 at bugs.launchpad.net
Tue May 19 19:05:26 UTC 2020


For the record, this bug should not affect a Charmed OpenStack
deployment, as it is handled by the following fix:

https://opendev.org/openstack/charm-nova-compute/commit/1869bfbc9711eac157821f8a4702409822c0842e
https://bugs.launchpad.net/charm-nova-compute/+bug/1839300

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to masakari in Ubuntu.
https://bugs.launchpad.net/bugs/1839715

Title:
  masakari fails if hypervisor name does not match nova service name

Status in masakari:
  In Progress
Status in masakari package in Ubuntu:
  Fix Released
Status in masakari source package in Eoan:
  Triaged
Status in masakari source package in Focal:
  Fix Released

Bug description:
  When adding a host to a segment masakari validates the provided
  hostname is a valid hypervisor name *1. But when masakari is mapping
  nova services *2 and servers *3 it uses the host attribute which may
  not necessarily match. It is common for the hypervisor entry to be a
  fqdn but service entry to be a bare hostname. In this situation both
  service and servers lookup fail and throw an IndexError.

  
  $ openstack hypervisor list -c ID -c "Hypervisor Hostname"
  +----+------------------------------------------------------+
  | ID | Hypervisor Hostname                                  |
  +----+------------------------------------------------------+
  |  1 | juju-f4bd71-zaza-9db566d782a2-18.project.serverstack |
  |  2 | juju-f4bd71-zaza-9db566d782a2-16.project.serverstack |
  |  3 | juju-f4bd71-zaza-9db566d782a2-17.project.serverstack |
  +----+------------------------------------------------------+

  $ openstack compute service list -c ID -c Binary -c Host
  +----+----------------+----------------------------------+
  | ID | Binary         | Host                             |
  +----+----------------+----------------------------------+
  |  1 | nova-conductor | juju-f4bd71-zaza-9db566d782a2-15 |
  |  2 | nova-scheduler | juju-f4bd71-zaza-9db566d782a2-15 |
  |  4 | nova-compute   | juju-f4bd71-zaza-9db566d782a2-18 |
  |  5 | nova-compute   | juju-f4bd71-zaza-9db566d782a2-16 |
  |  6 | nova-compute   | juju-f4bd71-zaza-9db566d782a2-17 |
  +----+----------------+----------------------------------+

  $ openstack server show 65419346-6509-4c73-b8f4-22c5aa7f0d77 -c 'OS-EXT-SRV-ATTR:host'
  +----------------------+----------------------------------+
  | Field                | Value                            |
  +----------------------+----------------------------------+
  | OS-EXT-SRV-ATTR:host | juju-f4bd71-zaza-9db566d782a2-18 |
  +----------------------+----------------------------------+

  
  *1 https://github.com/openstack/masakari/blob/master/masakari/compute/nova.py#L248
  *2 https://github.com/openstack/masakari/blob/master/masakari/compute/nova.py#L147
  *3 https://github.com/openstack/masakari/blob/master/masakari/compute/nova.py#L154

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



More information about the Ubuntu-openstack-bugs mailing list