Bug 1391169 - RHOSP:Register Nodes screen: While a node is being registered the next button is clickable.
Summary: RHOSP:Register Nodes screen: While a node is being registered the next button...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: WebUI
Version: 1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 1.1
Assignee: cchase
QA Contact: Sudhir Mallamprabhakara
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-02 17:23 UTC by James Olin Oden
Modified: 2016-11-22 20:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-22 20:33:05 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description James Olin Oden 2016-11-02 17:23:50 UTC
Description of problem:
I had created an OpenStack deployment, and I had gotten to the point where I had registered three of the four nodes I wanted to register in the RHOSP:Register Nodes screen.   I then clicked on "Add node to group" to register the last one, entered its MAC and clicked "Register".   When I did this the modal dialogue disappeared, and it began registering the new node.   However the "Next" was clickable before the node was finished registering.


Version-Release number of selected component (if applicable):
QCI-1.1-RHEL-7-20161101.t.0

How reproducible:
everytime

Steps to Reproduce:
1.   Create an Openstack deployment
2.   Work through the screens till you get to the RHOSP:Register Nodes screen.
3.   Now register all but one of your nodes.
4.  Click on "Add node to group", and enter the MAC of the remaining node.

Actual results:
The next button will be clickable before the node is finished registering.

Expected results:
The next button to not be clickable till the node is finished registering.


Additional info:

Comment 2 cchase 2016-11-22 20:33:05 UTC
Node registration can sometimes take awhile.  UX determined that we didn't want to hold the user at this screen if they already had 2 valid nodes for deployment since that was the minimum.


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