|Summary:||Volume Deletion Button Method Not Define|
|Product:||Red Hat CloudForms Management Engine||Reporter:||Nikhil Dhandre <ndhandre>|
|Component:||UI - OPS||Assignee:||Sam Lucidi <slucidi>|
|Status:||CLOSED ERRATA||QA Contact:||Nikhil Dhandre <ndhandre>|
|Version:||5.8.0||CC:||hkataria, jhajyahy, jhardy, mpovolny, ndhandre, obarenbo, simaishi|
|Fixed In Version:||188.8.131.52||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2019-02-07 23:02:39 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||Openstack||Target Upstream Version:|
Description Nikhil Dhandre 2017-08-31 13:26:29 UTC
Created attachment 1320590 [details] video Description of problem: Version-Release number of selected component (if applicable): Version 184.108.40.206.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:
Comment 2 Dave Johnson 2017-09-01 20:40:59 UTC
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?
Comment 3 Dave Johnson 2017-09-01 20:42:12 UTC
If this is new to 5.8.2, please mark regression keyword and propose blocker flag.
Comment 9 Sam Lucidi 2017-11-07 15:58:09 UTC
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.
Comment 11 Sam Lucidi 2017-11-07 21:08:27 UTC
Comment 14 Jad Haj Yahya 2018-07-02 17:05:04 UTC
Verified on 220.127.116.11
Comment 15 errata-xmlrpc 2019-02-07 23:02:39 UTC
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