Bug 1394751 - Unable to create snapshot for Cloud Volume status is: in-use.
Summary: Unable to create snapshot for Cloud Volume status is: in-use.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: GA
: cfme-future
Assignee: Marek Aufart
QA Contact: Ola Pavlenko
URL:
Whiteboard: openstack
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-14 11:51 UTC by Ronnie Rasouli
Modified: 2018-03-19 14:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-16 17:58:36 UTC
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:

Attachments (Terms of Use)
evm.log reproducing the issue (291.78 KB, text/plain)
2016-11-14 11:51 UTC, Ronnie Rasouli 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Ronnie Rasouli 2016-11-14 11:51:31 UTC 
Created attachment 1220367 [details]
evm.log reproducing the issue

Description of problem:

Create volume snapshot from an existing attached cloud volume fails

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

How reproducible:
100%

Steps to Reproduce:

1. Create an instance with attached volume to the instance
2. Browse to:Storage  --> Volumes	Cloud Volumes list
3. Select the volume which created on step 1	
4. Click configuration,  and select
Create snapshot from selected Cloud Volume

Actual results:
Unable to create snapshot for Cloud Volume "vol1": Expected([200, 202]) <=> Actual(400 Bad Request) excon.error.response :body => "{\"badRequest\": {\"message\": \"Invalid volume: Volume 2d500989-42ce-431d-8f84-57b65949311e status must be available, but current status is: in-use.\", \"code\"...

Expected results:

new snapshot from the attached volume

Additional info:
Comment 2 Ronnie Rasouli 2016-11-14 12:16:27 UTC 
In this case we should use a --force for an attached cloud volume
Comment 4 Sam Lucidi 2018-03-16 17:58:36 UTC 
The error here is the Cinder response to the action, and the UI appears to be working as intended.
Note You need to log in before you can comment on or make changes to this bug.