swift_rsync container restarts continuosly after upgrade to containerized deployment

Bug #1718403 reported by Christian Schwede
6
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
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (master)

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

description: updated
Changed in tripleo:
milestone: none → queens-1
importance: Undecided → High
Changed in tripleo:
milestone: queens-1 → queens-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (master)

Reviewed: https://review.openstack.org/505606
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=7c6e0a43c53c9dfce93ab89c5839198a8460d123
Submitter: Zuul
Branch: master

commit 7c6e0a43c53c9dfce93ab89c5839198a8460d123
Author: Christian Schwede <email address hidden>
Date: Wed Sep 20 13:47:08 2017 +0200

    Remove rsync from xinetd when upgrading to containerized deployment

    The rsync service needs to be removed from the xinetd service, otherwise
    the swift_rsync container will permanently restart because the rsync
    port (873) is still in use after upgrading.

    Closes-Bug: 1718403
    Change-Id: I283919891d00731c96ef963b0c4137d10144ccaf

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (stable/pike)

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/515448

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (stable/pike)

Reviewed: https://review.openstack.org/515448
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=1bc96c2b9c128c388414754d8abebd1d56dcd447
Submitter: Zuul
Branch: stable/pike

commit 1bc96c2b9c128c388414754d8abebd1d56dcd447
Author: Christian Schwede <email address hidden>
Date: Wed Sep 20 13:47:08 2017 +0200

    Remove rsync from xinetd when upgrading to containerized deployment

    The rsync service needs to be removed from the xinetd service, otherwise
    the swift_rsync container will permanently restart because the rsync
    port (873) is still in use after upgrading.

    Closes-Bug: 1718403
    Change-Id: I283919891d00731c96ef963b0c4137d10144ccaf
    (cherry picked from commit 7c6e0a43c53c9dfce93ab89c5839198a8460d123)

tags: added: in-stable-pike
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 7.0.5

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 8.0.0.0b2

This issue was fixed in the openstack/tripleo-heat-templates 8.0.0.0b2 development milestone.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.