Description of problem: OSP11 -> OSP12 upgrade: ceilometer agent services are running on host after compute nodes upgrade: [root@compute-1 heat-admin]# systemctl list-units --all | grep ceilometer openstack-ceilometer-compute.service loaded active running OpenStack ceilometer compute agent openstack-ceilometer-polling.service loaded active running OpenStack ceilometer polling agent There are no ceilometer containers running on the compute node so I'm wondering if these services should be removed from host and moved inside containers or removed alltogether: [root@compute-1 heat-admin]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 1aa6850acdff 192.168.24.1:8787/rhosp12/openstack-nova-compute-docker:2017-07-26.10 "kolla_start" 2 hours ago Up 14 minutes nova_compute dccbac08a18c 192.168.24.1:8787/rhosp12/openstack-iscsid-docker:2017-07-26.10 "kolla_start" 2 hours ago Up 2 hours iscsid 39787fd5c4ba 192.168.24.1:8787/rhosp12/openstack-nova-libvirt-docker:2017-07-26.10 "kolla_start" 2 hours ago Up 2 hours nova_libvirt Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-7.0.0-0.20170721174554.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy OSP11 2. Upgrade to OSP12 3. Check the openstack services running on the compute nodes: Actual results: [root@compute-1 heat-admin]# systemctl list-units --all | grep ceilometer openstack-ceilometer-compute.service loaded active running OpenStack ceilometer compute agent openstack-ceilometer-polling.service loaded active running OpenStack ceilometer polling agent Expected results: There are no openstack services running on the host. Additional info:
[root@compute-0 heat-admin]# systemctl list-units --all | grep ceilometer [root@compute-0 heat-admin]#
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