Bug 1492465

Summary: Nodes action buttons shouldn't be clickable and do any action if no nodes are registered
Product: Red Hat OpenStack Reporter: Ola Pavlenko <opavlenk>
Component: openstack-tripleo-uiAssignee: Jiri Tomasek <jtomasek>
Status: CLOSED ERRATA QA Contact: Udi Kalifon <ukalifon>
Severity: high Docs Contact:
Priority: high    
Version: 12.0 (Pike)CC: beth.white, jjoyce, jpichon, jrist, jschluet, jtomasek, slinaber, tvignaud
Target Milestone: Upstream M1Keywords: OtherQA, Regression, Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-ui-8.1.1-0.20180122135122.aef02d8.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 13:36:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ola Pavlenko 2017-09-17 13:58:45 UTC
Description of problem:
When no nodes are registered in UI, all buttons in nodes tab are "disabled"
Despite this, "tag nodes " and other options are clickable and actionable
Clicking on "Tag nodes" for example pops up "Tag Nodes into Profiles" window 

Version-Release number of selected component (if applicable):
openstack-tripleo-ui-7.3.1-0.20170830131652.f61181a.el7ost.noarch

How reproducible:


Steps to Reproduce:
1. delete default plan so there are no plans in UI
2. delete all nodes
3. on Nodes tab choose "tag nodes" 

Actual results:
"Tag Nodes into Profiles" window  pops up 
closing the pop up window turns all buttons to "available"

Expected results:
Button is disabled and not actionable

Additional info:

Comment 3 Jiri Tomasek 2017-10-02 15:22:48 UTC
Fixed by https://review.openstack.org/508910

Comment 7 Jason E. Rist 2018-04-05 21:57:42 UTC
definitely fixed in openstack-tripleo-ui-8.3.1-2.el7ost.noarch

Comment 9 errata-xmlrpc 2018-06-27 13:36:16 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:2086