Monasca Agent Libvirt issues with unqualified hostname
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
In Progress
|
Undecided
|
Mariusz Karpiarz |
Bug Description
In an environment where hypervisors are identified with their FQDNs:
```
$ openstack compute service list | grep compute-intel01
| 34 | nova-compute | compute-
```
and with monasca-
```
[centos@
hostname: compute-intel01
[centos@
...
2020-09-03 09:17:16 UTC | WARNING | collector | monasca_
2020-09-03 09:17:16 UTC | ERROR | collector | monasca_
2020-09-03 09:17:16 UTC | ERROR | collector | monasca_
...
```
The above results in the list of instances for this host being empty and no instance-related metrics coming from the Libvirt plugin.
Removing the "hostname" config parameter fixes the problem:
```
[centos@
#hostname: compute-intel01
[centos@
...
2020-09-03 09:18:53 UTC | INFO | collector | monasca_
2020-09-03 09:18:54 UTC | INFO | collector | monasca_
...
```
This is because the Agent cannot match unqualified "hostname" parameter against the fully-qualified hypervisor name:
https:/
The Agent can work out the hostname of the node it's running on automatically (using `hostname -f`) but the config parameter takes precedence:
https:/
Therefore I suggest we either remove the "hostname" parameter entirely or use `ansible_fqdn` instead.
Changed in kolla-ansible: | |
assignee: | nobody → Mariusz Karpiarz (mkarpiarz) |
status: | New → In Progress |
Hi Mariusz, are you still interested in working on this?