Problem Description The ring power determines the partition to which a resource (account, container or object) is mapped. The partition is included in the path under which the resource is stored in a backend filesystem. Changing the partition power therefore requires relocating resources to new paths in backend filesystems. In a heavily populated cluster a relocation process could be time-consuming and so to avoid down-time it is desirable to relocate resources while the cluster is still operating. However, it is necessary to do so without (temporary) loss of access to data and without compromising the performance of processes such as replication and auditing. http://specs.openstack.org/openstack/swift-specs/specs/in_progress/increasing_partition_power.html
https://github.com/openstack/swift-specs/blob/master/specs/in_progress/increasing_partition_power.rst
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Moving to 11 for triage and prio per discussion with the Swift squad. Resetting acks for reassessment.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462