Ocata -> Pike upgrade leaves clustercheck xinetd service running on the host
Bug #1706612 reported by
Damien Ciabrini
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
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) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/487889
Review: https:/