Looks like collectd container is restarting on overcloud deployt at a noop change, for scenario001
http://logs.openstack.org/45/560445/99/check/tripleo-ci-centos-7-scenario001-multinode-oooq-container/bf6c481/logs/undercloud/home/zuul/overcloud_deploy.log.txt.gz#_2018-07-30_02_16_20
2018-07-30 02:16:20 | TASK [Check for unhealthy containers after step 5] *****************************
2018-07-30 02:16:20 | task path: /var/lib/mistral/overcloud/common_deploy_steps_tasks.yaml:231
2018-07-30 02:16:20 | Monday 30 July 2018 02:11:13 +0000 (0:00:00.203) 0:42:35.574 ***********
2018-07-30 02:16:20 | ok: [centos-7-ovh-gra1-0001043637] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
2018-07-30 02:16:20 |
2018-07-30 02:16:20 |
2018-07-30 02:16:20 | TASK [Debug output for task which failed: Check for unhealthy containers after step 5] ***
2018-07-30 02:16:20 | task path: /var/lib/mistral/overcloud/common_deploy_steps_tasks.yaml:272
2018-07-30 02:16:20 | Monday 30 July 2018 02:16:16 +0000 (0:05:03.627) 0:47:39.202 ***********
2018-07-30 02:16:20 | fatal: [centos-7-ovh-gra1-0001043637]: FAILED! => {
2018-07-30 02:16:20 | "failed_when_result": true,
2018-07-30 02:16:20 | "outputs.stdout_lines|default([])|union(outputs.stderr_lines|default([]))": [
2018-07-30 02:16:20 | "6dfca3fff517 192.168.24.1:8787/tripleomaster/centos-binary-collectd:current-tripleo-updated-20180730001257 \"kolla_start\" 7 minutes ago Restarting (1) 16 seconds ago collectd"
2018-07-30 02:16:20 | ]
2018-07-30 02:16:20 | }
2018-07-30 02:16:20 |
2018-07-30 02:16:20 | NO MORE HOSTS LEFT *************************************************************
2018-07-30 02:16:20 |
2018-07-30 02:16:20 | PLAY RECAP *********************************************************************
2018-07-30 02:16:20 | centos-7-ovh-gra1-0001043637 : ok=211 changed=96 unreachable=0 failed=1
2018-07-30 02:16:20 | undercloud : ok=23 changed=12 unreachable=0 failed=0
2018-07-30 02:16:20 |
2018-07-30 02:16:20 | Monday 30 July 2018 02:16:16 +0000 (0:00:00.106) 0:47:39.309 ***********
2018-07-30 02:16:20 | ===============================================================================
2018-07-30 02:16:20 |
2018-07-30 02:16:20 | Ansible failed, check log at /var/lib/mistral/overcloud/ansible.log.
2018-07-30 02:16:20 | + status_code=1
2018-07-30 02:1
Also from the collectd container starting at the overcloud
http://logs.openstack.org/45/560445/99/check/tripleo-ci-centos-7-scenario001-multinode-oooq-container/bf6c481/logs/subnode-2/var/log/extra/docker/containers/collectd/stdout.log.txt.gz
++ cat /run_command
+ CMD='/usr/sbin/collectd -f'
+ ARGS=
+ [[ ! -n '' ]]
+ . kolla_extend_start
++ [[ ! -d /var/log/kolla/collectd ]]
+++ stat -c %a /var/log/kolla/collectd
++ [[ 2755 != \7\5\5 ]]
++ chmod 755 /var/log/kolla/collectd
+ echo 'Running command: '\''/usr/sbin/collectd -f'\'''
+ exec /usr/sbin/collectd -f
Running command: '/usr/sbin/collectd -f'
plugin_load: plugin "python" successfully loaded.
[2018-07-30 02:09:01] plugin_load: plugin "logfile" successfully loaded.
Error: Reading the config file failed!
Read the logs for details.
+ sudo -E kolla_set_configs
INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json
INFO:__main__:Validating config file
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__main__:Copying service configuration files
Looks like health check is kind of new https:/
Maybe it needs some tunning.