Bug 1449319 - Create a snapshot of this volume action is missing in Block storage volume list configuration menu
Summary: Create a snapshot of this volume action is missing in Block storage volume li...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.9.0
Assignee: Aparna Karve
QA Contact: Matouš Mojžíš
URL:
Whiteboard: ui:volume:ec2
Depends On:
Blocks: 1460024
TreeView+ depends on / blocked
 
Reported: 2017-05-09 15:30 UTC by Matouš Mojžíš
Modified: 2018-09-20 16:12 UTC (History)
6 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1460024 (view as bug list)
Environment:
Last Closed: 2018-03-06 15:11:48 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Matouš Mojžíš 2017-05-09 15:30:48 UTC 
Description of problem:


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

How reproducible:
Always

Steps to Reproduce:
1. Have an ec2 provider
2. Have a block storage volume
3. Go to Storage -> Block Storage -> Volumes
4. Check a volume and open configuration menu
5. Then go to volume summary and open configuration menu

Actual results:
In Block Storage Volume list configuration menu is missing "Create a snapshot of this volume"

Expected results:


Additional info:
Comment 2 Aparna Karve 2017-05-18 16:41:20 UTC 
Creating a volume is possible from the Cloud Volume Summary page but not from the Cloud Volume list view.

I believe we need a button for "Create a Snapshot" visible and functional from the list view too.

Working on this with Gregor Berginc.
Comment 3 Aparna Karve 2017-05-22 18:11:29 UTC 
PR: https://github.com/ManageIQ/manageiq-ui-classic/pull/1388
Comment 5 Matouš Mojžíš 2017-12-13 16:55:34 UTC 
Verified in 5.9.0.12. Action was added to volume list and is working correctly.
Note You need to log in before you can comment on or make changes to this bug.