Bug 1319812 - Cloudforms greyed out when starting a new deployment, selecting a provider and then going step back
Summary: Cloudforms greyed out when starting a new deployment, selecting a provider an...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: WebUI
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: TP3
: 1.0
Assignee: Erik Nelson
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks: rhci-sprint-14
TreeView+ depends on / blocked
 
Reported: 2016-03-21 15:08 UTC by Antonin Pagac
Modified: 2016-04-29 16:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-30 13:48:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Antonin Pagac 2016-03-21 15:08:30 UTC
Description of problem:
The Cloudforms image on the New Deployment page is not clickable and greyed out when coming back to the New Deployment page from step 1A using the Back button.

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

How reproducible:
Always

Steps to Reproduce:
1. Go to New Deployment page, select RHEV or OSP or both
2. Hit 'Select'
3. Remember that you wanted also CFME, so go back using the 'Back' button
4. CFME is greyed out and not clickable even when RHEV or OSP or both are selected

Actual results:
CFME not clickable

Expected results:
CFME should be clickable

Additional info:
Workaround: Unselect the provider you choose previously and then select it again.

Comment 1 Jesus M. Rodriguez 2016-03-30 13:48:56 UTC
We are working on a new product picker which completely changes the product selection screen. 

https://trello.com/c/6yXjgSx3/888-revise-product-picker-design-heard-more-than-a-few-comments-that-the-tiles-didn-t-initially-look-selectable

Closing this bug as the page is no longer relevant. We have made a note on the trello card to ensure the state transitions work to avoid this scenario.


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