Ocata -> Pike upgrade leaves clustercheck xinetd service running on the host

Bug #1706612 reported by Damien Ciabrini on 2017-07-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Damien Ciabrini

Bug Description

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.

tags: added: containers
Changed in tripleo:
status: New → Triaged
importance: Undecided → High
milestone: none → pike-rc1
Changed in tripleo:
assignee: nobody → Damien Ciabrini (dciabrin)

Fix proposed to branch: master
Review: https://review.openstack.org/487889

Changed in tripleo:
status: Triaged → In Progress

Reviewed: https://review.openstack.org/487889
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=090b33ed3b28a79eae25e4da02bb3201dba9bbf0
Submitter: Jenkins
Branch: master

commit 090b33ed3b28a79eae25e4da02bb3201dba9bbf0
Author: Damien Ciabrini <email address hidden>
Date: Thu Jul 27 14:41:16 2017 +0000

    Do not run clustercheck on the host after O->P upgrade

    Once an Ocata overcloud is upgraded to Pike, clustercheck should only be
    running in a dedicated container, and xinetd should no longer manage it on
    the host. Fix the mysql upgrade_task accordingly.

    Change-Id: I01acacc2ff7bcc867760b298fad6ff11742a2afb
    Closes-Bug: #1706612

Changed in tripleo:
status: In Progress → Fix Released

This issue was fixed in the openstack/tripleo-heat-templates release candidate.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers