b7a1b5b2cf
In a replication setup, users encountered a critical issue where they unintentionally reset the replica_state of an active replica while attempting to resolve errors on a non-active replica. This led to a situation with no active replica, causing data loss. Users expected server-side validation to prevent such actions. This commit implements the necessary validation in the codebase to ensure that the reset_replica_state action cannot be applied to active replicas, addressing the reported issue and improving data integrity in replication setups. Co-Authored-By: Solly <solobarine@gmail.com> Closes-Bug: #2015328 Change-Id: I629669476e585a834673b8c8b49ad4b0270b877f
7 lines
191 B
YAML
7 lines
191 B
YAML
---
|
|
fixes:
|
|
- |
|
|
The "replica_state" attribute of "active" replicas cannot be modified.
|
|
Please see `Launchpad bug 2015328 <https://launchpad.net/bugs/2015328>`_
|
|
for more details.
|