Replication freeze doesn't work as expected
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Gorka Eguileor |
Bug Description
Freeze functionality in the replication feature doesn't work as expected.
According to the specs [1]: "Freeze option provided as an argument to Failover The failover command includes a “freeze” option. This option indicates that a volume may still be read or written to, HOWEVER that we will not allow any additional resource create or delete options until an admin issues a “thaw” command."
Which is ratified by our devref documentation [2]: "freeze_backend Puts a backend host/service into a R/O state for the control plane. For example if a failover is issued, it is likely desirable that while data access to existing volumes is maintained, it likely would not be wise to continue doing things like creates, deletes, extends etc."
But we are not freezing half the operations we say we do. We can do deletes, create snapshots, delete snapshots...
The only mechanism that has been implemented is to disable the service in the scheduler, which means that only operations that go through the scheduler are frozen.
[1]: https:/
[2]: http://
Changed in cinder: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in cinder: | |
assignee: | nobody → Gorka Eguileor (gorka) |
Related fix proposed to branch: master /review. openstack. org/402922
Review: https:/