Bug 1516804 - Cloudforms: Unable to select multiple volumes during Cloud VM Provision through Lifecycle
Summary: Cloudforms: Unable to select multiple volumes during Cloud VM Provision throu...
Keywords:
Status: CLOSED DUPLICATE of bug 1506466
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: GA
: 5.9.0
Assignee: Greg McCullough
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-23 11:44 UTC by Imaan
Modified: 2017-12-06 06:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-23 13:01:17 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Imaan 2017-11-23 11:44:18 UTC
Description of problem:

Unable to select multiple volumes during Cloud VM Provision through Lifecycle.

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

5.9.0.9.20171115202245_7429f75

How reproducible:

Always

Steps to Reproduce:

1. Navigate to Compute -> Clouds -> Instances -> Lifecycle -> Provision instances -> Select any image -> Continue -> Volumes

2. Add multiple volumes 

3. Try to switch between tabs and again go to volumes tab, you will see only one item for volume.

Actual results:

Not able to select multiple volumes under volumes tabs.

Expected results:

The volume tab should contain multiple items under volume tab if user has added multiple volumes.

Comment 2 Dave Johnson 2017-11-23 12:02:40 UTC
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set the severity to Low.

Comment 3 Greg McCullough 2017-11-23 13:01:17 UTC

*** This bug has been marked as a duplicate of bug 1506466 ***


Note You need to log in before you can comment on or make changes to this bug.