Swift config changes are not applied on overcloud update

Bug #1802066 reported by Christian Schwede on 2018-11-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
High
Christian Schwede

Bug Description

Noticed this when adding a new disk to an existing deployment.

For example, adding disk vdb to an deployment that is currently using "d1" as the only device.

There are two issues after the deployment finished:

1. The rings in /var/lib/config-data/puppet-generated/swift/etc/swift are not updated (rings in /var/lib/config-data/swift_ringbuilder are updated, but not copied over)
2. Permissions on /srv/node are wrong

The issue here is that the one-time containers swift_setup_srv and swift_copy_rings are not run again.

tags: added: pike-backport-potential queens-backport-potential rocky-backport-potential
Changed in tripleo:
milestone: stein-2 → stein-3
Changed in tripleo:
assignee: Christian Schwede (cschwede) → Alex Schultz (alex-schultz)
Changed in tripleo:
assignee: Alex Schultz (alex-schultz) → Christian Schwede (cschwede)

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

commit b49629f085b5f04be999e0d5697a77e3791f7dcc
Author: Christian Schwede <email address hidden>
Date: Wed Nov 7 08:53:48 2018 +0100

    Do not ignore Swift ring changes to trigger container restart

    Swift containers need to restart if the rings change. In
    non-containerized environments this is not required, because the Swift
    processes will reload the rings on any changes. However, this does not
    work within containers, thus a restart is required.

    This also restarts swift_copy_rings and swift_setup_srv container. This
    will copy the updated ring files and ensure new storage mount points are
    using the right permissions.

    Closes-Bug: 1802066
    Related-Bug: 1786065
    Change-Id: Ie2b9f003dc34f2f02a45293d06d6a40c8d5ed8ff

Changed in tripleo:
status: In Progress → Fix Released

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

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

Other bug subscribers