Bug 1391103 - Deploy button should not be active (available) if no nodes were registered
Summary: Deploy button should not be active (available) if no nodes were registered
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Jiri Tomasek
QA Contact: Ola Pavlenko
RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-02 15:00 UTC by Jason E. Rist
Modified: 2017-02-01 16:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-01 16:14:04 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1637843 0 None None None 2016-11-02 15:00:35 UTC

Description Jason E. Rist 2016-11-02 15:00:32 UTC 
Cloned from launchpad bug 1637843.

Description:

UI with default pre-loaded plan but no registered nodes has "Verify and Deploy" button available for action.
Attempting to deploy will cause a "Failed deployment" which is correct, since no nodes are available for deployment, but having the deploy option available without nodes is confusing from the beginning.

System should not attempt to deploy if no nodes are available for the action.

Specification URL (additional information):

https://bugs.launchpad.net/tripleo/+bug/1637843
Comment 1 Ola Pavlenko 2017-02-01 16:13:48 UTC 
Jiri Tomasek (jtomasek) wrote on 2016-11-08:	#2
Making the deploy button disabled is IMHO going to bring more confusion due to the fact how we display nodes counts at the moment (see https://bugs.launchpad.net/tripleo/+bug/1640103)

The 'Validate and Deploy' button does not trigger any harmful operation. It brings up the summary view which provides the user with feedback on whether starting the deployment is safe or not. It is the up to the user to evaluate provided information and decide to start the deployment.
Note You need to log in before you can comment on or make changes to this bug.