[IBM Storwize_SVC] Able to create Volume -type, Volume, and snapshot with Invalid clean_rate

[Prajakta]

The valid range for clean_rate is 0-150 .
User is able to create a volume-type with invalid clean_rate of >150 with no warning/error msg .
User is also able to create Volume (in available state) and snapshot (error) with this volume -type and both can be seen in cinder list and cinder snapshot-list.
When we check at SVC backend , fcmap for the snapshot is not present at the backend indicating that the snapshot is not created at SVC and hence in error state , however in absence of a error/warning msg , user has no way to know this root cause .

No user warning/error msg displayed on console
The following error is shown in cinder.vol logs while creating snapshot

xpected response from the storage volume backend API: CLI Exception output:
Apr 08 09:09:15 altranvm2 cinder-volume[144871]: ERROR oslo_messaging.rpc.server command: ['svctask', 'mkfcmap', '-source', '"volume-3f1fff74-7450-4061-bb5d-63ac14bc816d"', '-target', '"snapshot-6c9c90be-1ecf-4598-b3d9-3fe706336071"', '-copyrate', '0', '-cleanrate', '155']
Apr 08 09:09:15 altranvm2 cinder-volume[144871]: ERROR oslo_messaging.rpc.server stdout:
Apr 08 09:09:15 altranvm2 cinder-volume[144871]: ERROR oslo_messaging.rpc.server stderr: CMMVC5703E The value or list starting with [155] is above the maximum permitted for that value or has exceeded the number of items allowed in a list.
Apr 08 09:09:15 altranvm2 cinder-volume[144871]: ERROR oslo_messaging.rpc.server .
Apr 08 09:09:15 altranvm2 cinder-volume[144871]: ERROR oslo_messaging.rpc.server
Apr 08 09:09:15 altranvm2 cinder-volume[144871]: DEBUG paramiko.transport [-] [chan 2044] EOF received (2044) {{(pid=144871) _log /usr/local/lib/python3.8/dist-packages/paramiko/channel.py:1212}}
Apr 08 09:09:15 altranvm2 cinder-volume[144871]: DEBUG paramiko.transport [-] [chan 2044] EOF sent (2044) {{(pid=144871) _log /usr/local/lib/python3.8/dist-packages/paramiko/channel.py:1212}}
Apr 08 09:09:15 altranvm2 cinder-volume[144871]: DEBUG oslo_concurrency.processutils [-] Result was 0 {{(pid=144871) ssh_execute /usr/local/lib/python3.8/dist-packages/oslo_concurrency/processutils.py:576}}
Apr 08 09:09:15 altranvm2 cinder-volume[144871]: DEBUG cinder.volume.drivers.ibm.storwize_svc.storwize_svc_common [-] Loopcall: vdisk snapshot-30b75161-3462-412c-afc4-8b168a9b39eb has more than one fc map. Waiting. {{(pid=144871) _check_vdisk_fc_mappings

[Prajakta (prajakta-belapurkar11)]

Cinder Version - Yoga

Cinder Backend - IBM Storwize_SVC

[Sofia Enriquez (lsofia-enriquez)]

Greetings Prajakta,

I could easily reproduce the problem.

cinder type-key ceph set clean_rate=200
cinder create 1 --volume-type ceph

No errors occur with either the type-key or the create commands. However, the volume ends up in error status so I can't take a snapshot.
Please let me know how you set the clean_rate in the extra specs or what other steps you take.

Thanks in advance

[Sofia Enriquez (lsofia-enriquez)]

Ignore my previous comment, this is IBM Storwize_SVC only-functionality.

https://docs.openstack.org/cinder/latest/configuration/block-storage/drivers/ibm-storwize-svc-driver.html

[Prajakta (prajakta-belapurkar11)]

This bus is invalid for IBM Storwize SVC

[Prajakta (prajakta-belapurkar11)]

Moving it to invalid state as suggested by the change owner
.Please refer below link for more details.
https://review.opendev.org/c/openstack/cinder/+/811877