scenario001 fails due to unhealthy collectd container

Bug #1784072 reported by Alex Schultz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Invalid
Critical
Unassigned

Bug Description

We're seeing the collecd container unhealthy in scenario001

2018-07-27 18:20:34 |
2018-07-27 18:20:34 | TASK [Debug output for task which failed: Check for unhealthy containers after step 5] ***
2018-07-27 18:20:34 | task path: /var/lib/mistral/overcloud/common_deploy_steps_tasks.yaml:272
2018-07-27 18:20:34 | Friday 27 July 2018 18:20:32 +0000 (0:05:03.909) 0:48:04.303 ***********
2018-07-27 18:20:34 | fatal: [centos-7-inap-mtl01-0001021431]: FAILED! => {
2018-07-27 18:20:34 | "failed_when_result": true,
2018-07-27 18:20:34 | "outputs.stdout_lines|default([])|union(outputs.stderr_lines|default([]))": [
2018-07-27 18:20:34 | "d8d48d041c9a 192.168.24.1:8787/tripleomaster/centos-binary-collectd:current-tripleo-updated-20180727161857 \"kolla_start\" 7 minutes ago Restarting (1) 52 seconds ago collectd"
2018-07-27 18:20:34 | ]
2018-07-27 18:20:34 | }

http://logs.openstack.org/95/586595/1/check/tripleo-ci-centos-7-scenario001-multinode-oooq-container/cee8408/logs/undercloud/home/zuul/overcloud_deploy.log.txt.gz#_2018-07-27_18_20_34

Revision history for this message
Alex Schultz (alex-schultz) wrote :

http://logs.openstack.org/23/579223/3/check/tripleo-ci-centos-7-scenario001-multinode-oooq-container/497581f/ passed after that job so maybe it's not still happening. Reopen this if this happens again

Changed in tripleo:
status: Triaged → Invalid
tags: removed: alert ci promotion-blocker
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.