Created attachment 1320590 [details] video Description of problem: Version-Release number of selected component (if applicable): Version 5.8.2.0.20170824192913_b09a5f8 How reproducible: Always Steps to Reproduce: 1. navigate to >> Storage > Block Storage > Volumes 2. Volume not available please add it. 3. Configuration > Delete this Cloud Volume Actual results: You will get Unexpected error Expected results: Button Method has to Implement. Additional info:
Is this with all providers supporting volume create which is OSP and EC2 only??? Is this with no providers and an issue of greying out the button? What happens in 5.8.1?
If this is new to 5.8.2, please mark regression keyword and propose blocker flag.
This appears to happen when the volume is queued to be deleted, and then another attempt to delete it is made before refresh has completed. On the back end the volume has already been removed, so the subsequent attempt fails. The delete volume functionality works correctly, but it needs some handling for this case.
https://github.com/ManageIQ/manageiq-providers-openstack/pull/147
Verified on 5.10.0.2
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:0212