NetApp cDOT doesn't set replication_enabled key when volumes are created with replication_enabled
Bug #1622057 reported by
Goutham Pacha Ravi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Goutham Pacha Ravi |
Bug Description
Steps to reproduce:
* Setup host-level replication with the NetApp cDOT driver
* Create a volume with replication_
* After the volume is created, see the volume details, replication_status is set to None, despite being on a backend that has replication enabled.
Failover sets the volume status correctly, but not volume creation.
Changed in cinder: | |
assignee: | nobody → Goutham Pacha Ravi (gouthamr) |
tags: | added: newton-rc-potential |
tags: |
added: newton-rc1-potential removed: newton-rc-potential |
summary: |
NetApp cDOT doesn't set replication_enabled key when volumes are created - with replication_type + with replication_enabled |
tags: |
added: newton-rc-potential removed: newton-rc1-potential |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/369620
Review: https:/