Hide Forgot
Description of problem: Ceilometer can't find nova instance because of name differences: it appears as compute-2 for ceilometer in ceilometer.conf (host = socket.gethostname()) and as host=compute-2.localdomain in nova.conf. So there are no events sent from that instance. There are several ways of workaround, from removing host= in nova.conf to adding it to ceilometer.conf.It should work by default so there should not be any need to add or remove host. You can add Ceilometer DFG to this bug Version-Release number of selected component (if applicable): openstack-nova-conductor-14.0.7-11.el7ost.noarch openstack-nova-scheduler-14.0.7-11.el7ost.noarch openstack-nova-cert-14.0.7-11.el7ost.noarch openstack-nova-api-14.0.7-11.el7ost.noarch openstack-nova-common-14.0.7-11.el7ost.noarch openstack-nova-compute-14.0.7-11.el7ost.noarch openstack-ceilometer-common-7.1.0-2.el7ost.noarch openstack-ceilometer-notification-7.1.0-2.el7ost.noarch openstack-ceilometer-central-7.1.0-2.el7ost.noarch openstack-ceilometer-api-7.1.0-2.el7ost.noarch openstack-ceilometer-collector-7.1.0-2.el7ost.noarch openstack-ceilometer-polling-7.1.0-2.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy puddle 2017-18-18.2 2. Create an instance 3. Observe the instance hostname Actual results: The names differ, no resource is found by ceilometer Expected results: The ceilometer must find the resource automatically Additional info:
If I'm not mistaken the nova.conf is correct, and the ceilometer.conf is wrong. So, I will move it to the Telemetry DFG for now.
This is only a problem for deployment where hosts do not have fully qualified hostname, e.g. they rely on localdomain.
*** Bug 1496388 has been marked as a duplicate of this bug. ***
openstack-tripleo-heat-templates-7.0.3-11.el7ost
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462