Bug 1497919 - OpsTools | Availability Monitoring | check-docker-health lists only the first unhealthy container
Summary: OpsTools | Availability Monitoring | check-docker-health lists only the firs...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
Target Milestone: beta
: 12.0 (Pike)
Assignee: Martin Magr
QA Contact: Leonid Natapov
Depends On:
TreeView+ depends on / blocked
Reported: 2017-10-03 06:43 UTC by Leonid Natapov
Modified: 2018-02-05 19:15 UTC (History)
4 users (show)

Fixed In Version: openstack-tripleo-heat-templates-7.0.3-0.20171023134947.8da5e1f.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 22:11:53 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1720972 0 None None None 2017-10-03 08:36:28 UTC
OpenStack gerrit 509110 0 None None None 2017-10-03 11:14:58 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Leonid Natapov 2017-10-03 06:43:38 UTC
Description of problem:

Check-docker-health check which is in the sensu_client container (/etc/sensu/conf.d/checks) should check for unhealthy containers and list them in its output. If there are few unhealthy containers it will list only the first one instead of listing all of them.

Comment 1 Martin Magr 2017-10-03 08:36:28 UTC
Linked upstream bug.

Comment 2 Martin Magr 2017-10-10 06:29:55 UTC
Patch and it's pike backport has been merged.

Comment 5 Leonid Natapov 2017-11-07 13:31:54 UTC

Comment 8 errata-xmlrpc 2017-12-13 22:11:53 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.