[Bug 1839715] Re: masakari fails if hypervisor name does not match nova service name
Launchpad Bug Tracker
1839715 at bugs.launchpad.net
Mon Feb 17 21:33:41 UTC 2020
This bug was fixed in the package masakari -
9.0.0~b2~git2020020609.8b122a8-0ubuntu2
---------------
masakari (9.0.0~b2~git2020020609.8b122a8-0ubuntu2) focal; urgency=medium
* d/p/allow-bare-hostnames.patch: Cherry pick inflight fix to allow use of
bare hostnames when adding hosts to segments (LP: #1839715).
* d/p/python3.8-compat.patch,skip-py38-failures.patch: Drop skip patch and
pick proposed fixes for Python 3.8 compatibility (LP: #1860265).
* d/rules: Ensure Python doctree's are not included in binary packages.
* d/control: Tidy lintian warnings with regards to package long
descriptions.
-- James Page <james.page at ubuntu.com> Mon, 17 Feb 2020 16:22:28 +0000
** Changed in: masakari (Ubuntu Focal)
Status: In Progress => Fix Released
--
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