[IBM]The storwize parameters are not correct when cinder create volume with "--source-replica"

Bug #1390001 reported by yixuan zhang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Invalid
Undecided
TaoBai

Bug Description

1. Create a volume type type-1 with storwize parameters change:
drivers:easytier=off
qos:IOThrottling=30000
2. Create a volume volume-1 with type-1.
Check the volume-1 from storage site,the parameters are correct;
drivers:easytier=off
qos:IOThrottling=30000

3. Create a volume with command
Cinder create --source-replica volume-1-id.

There is a new volume-2 creates with the clone of the replicated volume-1.
Check the volume-2 from the storage site.

It was found the
qos:IOThrottling=disabled.
drivers:easytier=on.

They should be the same with the initial volume-1.

Revision history for this message
TaoBai (baitao2020) wrote :

Thanks for you report this issue. I will work on it

Changed in cinder:
assignee: nobody → TaoBai (baitao2020)
Revision history for this message
TaoBai (baitao2020) wrote :

As confirmed with Ronen.
The cloned replica volume as current design does not have volume type. So that's the reason why cloned replica volume does not have parameter.

Revision history for this message
TaoBai (baitao2020) wrote :

https://etherpad.openstack.org/p/cinder-replication-redoc

In the Q&A part:

Q: The new volume created by create_replica_test_volume() does not have a volume-type associated, it's controled by cinder general, I am not sure whether this is a bug or work as design?
A2: This is by design. The volume type cannot be as for the original volume, it would be a replicated volume if so. Therefore I decided for allocate it with no volume-type.

Changed in cinder:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.