Bug 1487234

Summary: Volume Deletion Button Method Not Define
Product: Red Hat CloudForms Management Engine Reporter: Nikhil Dhandre <ndhandre>
Component: UI - OPSAssignee: Sam Lucidi <slucidi>
Status: CLOSED ERRATA QA Contact: Nikhil Dhandre <ndhandre>
Severity: high Docs Contact:
Priority: high    
Version: 5.8.0CC: hkataria, jhajyahy, jhardy, mpovolny, ndhandre, obarenbo, simaishi
Target Milestone: GA   
Target Release: 5.10.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-07 23:02:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Openstack Target Upstream Version:
Description Flags
video none

Description Nikhil Dhandre 2017-08-31 13:26:29 UTC
Created attachment 1320590 [details]

Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:

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 14 Jad Haj Yahya 2018-07-02 17:05:04 UTC
Verified on

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.