
The value of volume.replication_status for a replicated volume is 'disabled' before 'failover-host' and it is changed to "failed-over" after 'failover-host' command if active_backend_id is not equal to secondary array IP. It is changed to 'enabled' after another 'failover-host' command if active_backend_id is equal to secondary array IP(which is failback scenario). After failback, if replication is removed from replicated volume, then retype 'dedup without replication'<->'nodedup without replication' with '--migration-policy on-demand' is not working since value of volume.replication_status is enabled. Change-Id: I193572532a36eaea5d826cff76ca9f98df86dc50 Closes-Bug: #1616329 Co-Authored-By: VenkataKrishna Reddy<Venkata.Krishna.ctr@kaminario.com> Co-Authored-By: Lakshman<Lakshmi.Narayana.ctr@kaminario.com>
Release notes
The release notes for a patch should be included in the patch. The intended audience for release notes include deployers, administrators and end-users.
A release note is required if the patch has upgrade or API impact. It is also required if the patch adds a feature or fixes a long-standing or security bug.
Please see http://docs.openstack.org/developer/cinder/devref/releasenotes.html for more details.