ceilometer doesn't get instances data on machine due to invalid hostname

[Brooklyn]

ceilometer-acompute wont get data on the machine that with an invalid hostname returned by socket.getfqdn().

if ceilometer-acompute is running on a virtual machine, socket.getfqdn() would return an invalid hostname which is not recognized by nova.

[Julien Danjou (jdanjou)]

This is probably libvirt not supporting this, so it's not going to be a bug in Ceilometer AFAICT.

[Brooklyn (yuanotes)]

I found a solution for this.

The PollingTask in ceilometer/compute/manager.py need the "cfg.CONF.host" option to get all instances on current host.

If that's not configured in ceilometer.conf, it will use an incorrect hostname that won't any instances.

I am not sure whether it's caused by libvirt or not. I just add host=<HOSTNAME> in ceilometer.conf to solve this.

[Doug Hellmann (doug-hellmann)]

We should probably have the host default set to something obviously incorrect (an empty string?) and then have the code that needs the setting warn if it is not set, rather than returning bogus data or skipping the polling silently.

[John Tran (jtran)]

FWIW, although this is an invalid bug, it has affected me on numerous occasions and it wasn't very easy to troubleshoot.

[Brooklyn (yuanotes)]

I think this is not INVALID since this still affected me today.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/36635

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/36635
Committed: http://github.com/openstack/ceilometer/commit/16f8e14b24006b23e1965329fa27ab7fcab3e6de
Submitter: Jenkins
Branch: master

commit 16f8e14b24006b23e1965329fa27ab7fcab3e6de
Author: Brooklyn Chen <email address hidden>
Date: Thu Jul 11 19:11:11 2013 +0800

    Use correct hostname to get instances.

    socket.getfqdn() would return a fully qualified domain name
    which maybe invalid for nova to get instances by hostname.
    If the host that runs devstack is virtual(like running
    devstack on AWS), socket.getfqdn() may return a domain name
    which is not the host name and nova cannot use that to get
    instances running on current host.

    Fix bug: #1166717

    Change-Id: Ic6cc8607bcdeee720c5d46d44fbaa589b4fb950e

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/grizzly
Review: https://review.openstack.org/39474

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/39474
Committed: http://github.com/openstack/ceilometer/commit/c9129d1fd69a546f67517836f358e21f160ce994
Submitter: Jenkins
Branch: stable/grizzly

commit c9129d1fd69a546f67517836f358e21f160ce994
Author: Brooklyn Chen <email address hidden>
Date: Thu Jul 11 19:11:11 2013 +0800

    Use correct hostname to get instances.

    socket.getfqdn() would return a fully qualified domain name
    which maybe invalid for nova to get instances by hostname.
    If the host that runs devstack is virtual(like running
    devstack on AWS), socket.getfqdn() may return a domain name
    which is not the host name and nova cannot use that to get
    instances running on current host.

    Fix bug: #1166717

    Change-Id: Ic6cc8607bcdeee720c5d46d44fbaa589b4fb950e
    (cherry picked from commit 16f8e14b24006b23e1965329fa27ab7fcab3e6de)