swift_rsync container restarts continuosly after upgrade to containerized deployment
Bug #1718403 reported by
Christian Schwede
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Christian Schwede |
Bug Description
Non-containerized deployments use xinetd to execute the rsync service needed by Swift.
After upgrading from a non-containerized deployment to a containerized xinetd is still running, and using port 873 (rsync). Thus the swift_rsync container can't start, because the port is still in use.
Therefore the upgrade tasks needs to stop the xinetd service as well.
Changed in tripleo: | |
assignee: | nobody → Christian Schwede (cschwede) |
status: | New → In Progress |
description: | updated |
Changed in tripleo: | |
milestone: | none → queens-1 |
importance: | Undecided → High |
Changed in tripleo: | |
milestone: | queens-1 → queens-2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/505606
Review: https:/