Description of problem: A freshly installed RHOSP 16.2 when integrated to a Dell PowerStore, fails to delete volumes. Creation and attachment work fine. Version-Release number of selected component (if applicable): cinder-volume-16.2.5-3 How reproducible: * Deploy RHOSP 16.2 * Integrate it with the Dell PowerStore solution. Use this for reference: https://github.com/dell/osp-integration/tree/master/osp-deploy/cinder * Create a volume using cinder (works). * Try to delete it. (fails) Steps to Reproduce: 1. Deploy RHOSP 16.2 2. Integrate it with the Dell PowerStore solution. Use this for reference: https://github.com/dell/osp-integration/tree/master/osp-deploy/cinder 3. Create a volume using cinder (works) 4. Try to delete it. (fails) Actual results: We get a "deletion failed" message. Expected results: The volume should be deleted without issue. Additional info: This is the error we found in cinder-volume's logs: 2023-05-02 13:22:28.830 163 ERROR cinder.volume.drivers.dell_emc.powerstore.client [req-96a37e5f-b260-4afe-aba2-136429680206 cf2c60455e6046578023ee4a2f9002f9 b1022502fb404efaacc3736d32d36126 - default default] REST Request: DELETE https://172.29.211.6/api/rest/volume/804f0ae3-18e3-4b8e-964c-aeb20705b86b with body {} 2023-05-02 13:22:28.830 163 ERROR cinder.volume.drivers.dell_emc.powerstore.client [req-96a37e5f-b260-4afe-aba2-136429680206 cf2c60455e6046578023ee4a2f9002f9 b1022502fb404efaacc3736d32d36126 - default default] REST Response: 400 with data {"messages":[{"code":"0xE0404003000B","severity":"Error","message_l10n":"The REST body parameter is not accepted.","arguments":[""]}]} 2023-05-02 13:22:28.830 163 ERROR cinder.volume.drivers.dell_emc.powerstore.client [req-96a37e5f-b260-4afe-aba2-136429680206 cf2c60455e6046578023ee4a2f9002f9 b1022502fb404efaacc3736d32d36126 - default default] Failed to delete PowerStore volume with id 804f0ae3-18e3-4b8e-964c-aeb20705b86b. There is a fix here: https://github.com/openstack/cinder/commit/a4ab9220fcfd4afd3019a0f3bd4f4b452296166f
Vagner: thanks for reporting back, glad to know that the fix proposed for BZ #2185565 seems to work. Since your work here is done, I'm going to close this as a duplicate of 2185565. *** This bug has been marked as a duplicate of bug 2185565 ***