Bug 1475348 - OSP11 -> OSP12 upgrade: leaves clustercheck xinetd service running on the host
Summary: OSP11 -> OSP12 upgrade: leaves clustercheck xinetd service running on the host
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: beta
: 12.0 (Pike)
Assignee: Damien Ciabrini
QA Contact: Marius Cornea
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-26 13:28 UTC by Marius Cornea
Modified: 2018-02-05 19:10 UTC (History)
9 users (show)

Fixed In Version: openstack-tripleo-heat-templates-7.0.0-0.20170913050524.0rc2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-13 21:44:48 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1706612 0 None None None 2017-07-26 13:29:14 UTC
OpenStack gerrit 487889 0 None None None 2017-08-14 13:50:40 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 Marius Cornea 2017-07-26 13:28:35 UTC 
When performing a major upgrade from a non-containerized Ocata to a containerized Pike, a new
container dedicated to galera's clustercheck is created to serve galera healthcheck queries on port 9200.

However, the clustercheck service is still configured on the xinet daemon running on the host, and after the upgrade that port is still held and served by xinetd on the host.
Comment 1 Michele Baldessari 2017-08-14 13:50:41 UTC 
Upstream reviews has just been +Aed
Comment 2 Michele Baldessari 2017-08-16 07:35:51 UTC 
Upstream review has merged, moving to POST
Comment 7 errata-xmlrpc 2017-12-13 21:44:48 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/RHEA-2017:3462
Note You need to log in before you can comment on or make changes to this bug.