Ceilometer-agent-central not running even though playbooks successfully run

Bug #1519423 reported by Miguel Alejandro Cantu
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
High
Miguel Alejandro Cantu
Liberty
Fix Released
High
Miguel Alejandro Cantu
Trunk
Fix Released
High
Miguel Alejandro Cantu

Bug Description

The ceilometer-agent-central agent will not come up and no information is giving by upstart when attempted to start the service.
In addition, the appropriate ceilometer-agent-central.log is not generated as well, so the problem causing the service to fail isn't very clear.
The ansible playbooks miss this as well; successfully running even though the ceilometer-agent-central service never successfully starts.

Changed in openstack-ansible:
status: New → In Progress
assignee: nobody → Miguel Alejandro Cantu (miguel-cantu)
Revision history for this message
Miguel Alejandro Cantu (miguel-cantu) wrote :

Ceilometer-agent-central backwards compatibility has been removed in Liberty, and the proper way to load pollsters is though ceilometer-polling now. This means that the upstart init scripts will need to change.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible (master)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible (liberty)

Fix proposed to branch: liberty
Review: https://review.openstack.org/249946

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible (master)

Reviewed: https://review.openstack.org/249881
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=603f7b4deee1f1fa90ed014714384feb33b1e1ab
Submitter: Jenkins
Branch: master

commit 603f7b4deee1f1fa90ed014714384feb33b1e1ab
Author: Miguel Alex Cantu <email address hidden>
Date: Wed Nov 25 16:09:10 2015 +0000

    Added ceilometer-polling upstart jobs

    The ceilometer-central-agent and ceilometer-agent-compute
    services are now completely removed from the liberty release
    of ceilometer. The new implementation is to use ceilometer-polling
    and call the respective pollsters by namespace.
    This patch addes the neccessary upstart configurations for
    ceilometer-polling and it also removes the deprecated admin_* options
    from the ceilometer config file.
    This patch set is also forcing ceilometer to use the Keystone
    v2.0 API by adding the versioned path uder [service_credentials]
    in the ceilometer config file.

    Change-Id: Iba2bb148df4f3ae9d16b44c27ddff0c0d3fd29d3
    UpgradeImpact
    Closes-Bug: #1519423
    Closes-Bug: #1519462

Changed in openstack-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible (liberty)

Reviewed: https://review.openstack.org/249946
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=c0de22d61e7a897ab5bdd31a3dfebe2acd7f4d60
Submitter: Jenkins
Branch: liberty

commit c0de22d61e7a897ab5bdd31a3dfebe2acd7f4d60
Author: Miguel Alex Cantu <email address hidden>
Date: Wed Nov 25 16:09:10 2015 +0000

    Added ceilometer-polling upstart jobs

    The ceilometer-central-agent and ceilometer-agent-compute
    services are now completely removed from the liberty release
    of ceilometer. The new implementation is to use ceilometer-polling
    and call the respective pollsters by namespace.
    This patch addes the neccessary upstart configurations for
    ceilometer-polling and it also removes the deprecated admin_* options
    from the ceilometer config file.
    This patch set is also forcing ceilometer to use the Keystone
    v2.0 API by adding the versioned path uder [service_credentials]
    in the ceilometer config file.

    Change-Id: Iba2bb148df4f3ae9d16b44c27ddff0c0d3fd29d3
    UpgradeImpact
    Closes-Bug: #1519423
    Closes-Bug: #1519462
    (cherry picked from commit 603f7b4deee1f1fa90ed014714384feb33b1e1ab)

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 12.0.8

This issue was fixed in the openstack/openstack-ansible 12.0.8 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 12.0.9

This issue was fixed in the openstack/openstack-ansible 12.0.9 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 13.0.0

This issue was fixed in the openstack/openstack-ansible 13.0.0 release.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :

This issue was fixed in the openstack/openstack-ansible 13.0.0 release.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 12.0.11

This issue was fixed in the openstack/openstack-ansible 12.0.11 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.