`neutron_service_check.py` can't list agents about rpc-maas HOT 4 CLOSED

If it works when you run it by hand, I wonder if it's a problem with how we register the check with ansible. @mattt416 what do you think?

from rpc-maas.

Hi @jpmontez,

Whilst that manual command runs fine, the plugin check should actually be of the format neutron_service_check.py --host <ansible_hostname> <internal_vip_address>. It sounds like we may be passing in the wrong hostname which neutron does not recognise.

Are you able to provide me with more details about how the check was registered (file, args, etc.)? I'll take a look at our playbooks in more detail now to see if I can spot any issues.

Thanks!

--Matt

from rpc-maas.

File: neutron_service_check.py
Arguments: --host 573955-compute07 192.168.96.10
Entity Label: 573955-compute07.qe1.iad3.rackspace.com

When I use the FQDN, it's successful:

root@569038-infra02:/usr/lib/rackspace-monitoring-agent/plugins# ./neutron_service_check.py --host 573955-compute07.qe1.iad3.rackspace.com 192.168.96.10
status okay
metric neutron-linuxbridge-agent_status uint32 1

It looks like the FQDN needs to be passed as an argument, not the hostname.

from rpc-maas.

Created rcbops/ansible-lxc-rpc#452 to deal w/ this (as the issue exists in the playbooks rather than with the script itself).

from rpc-maas.