Bug 1542493 - Customization of container health checks when defining non standard port
Summary: Customization of container health checks when defining non standard port
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 12.0 (Pike)
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: z2
: 13.0 (Queens)
Assignee: Martin Magr
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-06 13:02 UTC by Benjamin Schmaus
Modified: 2018-12-24 11:40 UTC (History)
9 users (show)

Fixed In Version: openstack-tripleo-heat-templates-8.0.3-2.el7ost
Doc Type: Bug Fix
Doc Text:
If you use a non-standard port for RabbitMQ instance that is for monitoring purposes, the sensu-client container reported an unhealthy state due to not reflecting the port value in the container health check. The port value now shows in the container health check.
Clone Of:
Environment:
Last Closed: 2018-08-29 16:34:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 545280 0 None master: MERGED tripleo-heat-templates: Use sensu-client healthcheck parameter (Icc01ce23b3fc538811b4dfc4fbaba18dc7165f89) 2018-07-19 14:54:54 UTC
OpenStack gerrit 563030 0 None stable/queens: MERGED tripleo-heat-templates: Use sensu-client healthcheck parameter (Icc01ce23b3fc538811b4dfc4fbaba18dc7165f89) 2018-07-19 14:54:49 UTC
Red Hat Product Errata RHBA-2018:2574 0 None None None 2018-08-29 16:35:49 UTC

Description Benjamin Schmaus 2018-02-06 13:02:59 UTC
Description of problem:  When a customer deploys using a non standard port for an OSP service they should also be able to customize the port used for the health check.  Setting this port in the sensu-client.yaml does not appear to work


Version-Release number of selected component (if applicable):
OSP12

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 25 Joanne O'Flynn 2018-08-15 07:56:28 UTC
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible.

If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-".


To add draft documentation text:

* Select the documentation type from the "Doc Type" drop down field.

* A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.

Comment 27 errata-xmlrpc 2018-08-29 16:34:51 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.

https://access.redhat.com/errata/RHBA-2018:2574


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