Bug 1337057

Summary:	Remove Cinder volume fails - "No Cloud Volumes were selected for deletion."
Product:	Red Hat CloudForms Management Engine	Reporter:	Ronnie Rasouli <rrasouli>
Component:	Providers	Assignee:	Scott Seago <sseago>
Status:	CLOSED ERRATA	QA Contact:	Ola Pavlenko <opavlenk>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.6.0	CC:	gblomqui, jfrey, jhajyahy, jhardy, maufart, mfeifer, obarenbo, simaishi
Target Milestone:	GA
Target Release:	5.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.6.0.8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-29 16:03:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ronnie Rasouli 2016-05-18 07:47:33 UTC

Description of problem:

CFME failed to delete a volume from volume list with a false negative message.

"No Cloud Volumes were selected for deletion."

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

5.6.0 Beta 2.5

How reproducible:
100%

Steps to Reproduce:
1. Login to the Cloudforms UI
2. Go to Compute --> Clouds --> Volumes
3. Select a volume
4. Go to configuration and choose Delete selected Cloud Volumes
Actual results:
Delete failed
"No Cloud Volumes were selected for deletion."


Expected results:
The cloud volume should be removed from volume list


Additional info:

Comment 2 Marek Aufart 2016-05-18 08:17:56 UTC

PR fixing this bug is on review - https://github.com/ManageIQ/manageiq/pull/8772

Comment 3 Tzu-Mainn Chen 2016-06-02 14:19:40 UTC

This has been backported already.

Comment 4 Ronnie Rasouli 2016-06-08 07:50:02 UTC

Verify failed, the delete works and trigger delete on cloud provider.

However, the volume list in UI doesn't change

Comment 7 errata-xmlrpc 2016-06-29 16:03:38 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/RHBA-2016:1348