Cause: Swift rings became inconsistent when new storage or controller nodes were added or existing ones replaced.
Consequence: Unavailability of data and increased and infinite replication between storage nodes, leading to higher load and network traffic.
Fix: A new process stores a copy of them on the undercloud after each deployment, and retrieves them before any new deployment or update to ensure consistency across all nodes. This removes the need to manually maintaining and copying them across nodes.
Result: Simplified deployment of new or replaced nodes using Swift storage.