Description of problem:
After deploying containerized OSP12 with opstools templates ,sensu-client and collectd containers were created only on controller. Should be created on all overcloud nodes.
Deploy command I used:
openstack overcloud deploy --templates --libvirt-type kvm --ntp-server clock.redhat.com --control-scale 1 --control-flavor controller --compute-scale 1 --compute-flavor compute -e /home/stack/virt/network/network-environment.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/docker.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/services-docker/sensu-client.yaml -e monitoring.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/services-docker/collectd.yaml -e local_config.yaml -e docker-osp12.yaml
Only on controller I see:
d399ac65bf6d 192.168.24.1:8787/rhosp12/openstack-sensu-client-docker:2017-07-02.2 "kolla_start" 8 hours ago Up 8 hours sensu_client
9b5f3e7c546f 192.168.24.1:8787/rhosp12/openstack-collectd-docker:2017-07-02.2 "kolla_start" 8 hours ago Up 8 hours
Those containers should be created on all overcloud nodes.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Would like a bit more information here.
The SensuClient should be included in all roles by default now:
This could be caused by an environmental custom heat parameter that overrides the list of services for the compute role. Is ComputeServicesDefault getting set anywhere in the custom environment variables?
Leonid - can you please check the configuration files, even better if you can attach them to the Bz for dprince review.
(In reply to Omri Hochman from comment #2)
> Leonid - can you please check the configuration files, even better if you
> can attach them to the Bz for dprince review.
Sure,Omri. What files exactly do you want me to attach ?
sensu,fluentd and colletcd included in all roles by default,that's true.
I checked the role files of Controller,Compute and others.
I took a look at the environment and this is what I saw getting configured in this environment:
(undercloud) [stack@undercloud-0 ~]$ openstack stack show overcloud | grep ComputeServices
| | ComputeServices: OS::TripleO::Services::NovaCompute,OS::TripleO::Services::NovaLibvirt,OS::TripleO::Services::ComputeNeutronOvsAgent,OS::TripleO::Services::Docker,OS::TripleO::Services::CeilometerAgentCompute,OS::TripleO::Services::Sshd
This matches what is hard coded in the environments/docker.yaml upstream which would explain why you don't see SensuClient in this list... because it isn't there.
It looks like we need to reconcile this upstream and get the ComputeServices correctly represented a single location (probably role_data.yaml).
In short this is a valid bug.
We'll need to sort this out upstream:
https://review.openstack.org/481747 Drop ComputeServices from environments/docker.yaml
If you want to try cherry-picking the fix downstream it should be safe to do so. Alternately you could explicitly specify your a custom ComputeServices heat parameter that matches the setting in roles_data.yaml to get the same effect. Either of these solutions would be a valid work around to this issue for now.
Moving to POST since the upstream fix was merged.
[root@overcloud-compute-0 heat-admin]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
315dcdb63921 192.168.24.1:8787/rhosp12/openstack-nova-compute-docker:2017-07-26.10 "kolla_start" 26 minutes ago Up 26 minutes nova_compute
f73e2070137b 192.168.24.1:8787/rhosp12/openstack-iscsid-docker:2017-07-26.10 "kolla_start" 30 minutes ago Up 30 minutes iscsid
04e8e89c5bf5 192.168.24.1:8787/rhosp12/openstack-nova-libvirt-docker:2017-07-26.10 "kolla_start" 30 minutes ago Up 30 minutes nova_libvirt
0a697fd352af 192.168.24.1:8787/rhosp12/openstack-collectd-docker:2017-07-26.10 "kolla_start" 30 minutes ago Up 30 minutes collectd
ed3299b671b3 192.168.24.1:8787/rhosp12/openstack-sensu-client-docker:2017-07-26.10 "kolla_start" 30 minutes ago Up 30 minutes sensu_client
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.