| Summary: | Unable to create snapshot for Cloud Volume status is: in-use. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Ronnie Rasouli <rrasouli> | ||||
| Component: | Providers | Assignee: | Marek Aufart <maufart> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Ola Pavlenko <opavlenk> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 5.7.0 | CC: | jfrey, jhardy, obarenbo, slucidi | ||||
| Target Milestone: | GA | ||||||
| Target Release: | cfme-future | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | openstack | ||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-03-16 17:58:36 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | Openstack | Target Upstream Version: | |||||
| Attachments: |
|
||||||
In this case we should use a --force for an attached cloud volume The error here is the Cinder response to the action, and the UI appears to be working as intended. |
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: