Created attachment 1091726 [details] node power Description of problem: The OpenStack Platform Director nodes details should not show the power actions button as no power operations are supported for these type of nodes. The Power button is active but shows an empty list of actions. Version-Release number of selected component (if applicable): 5.5.0.9-beta2.20151102161742_5530c9a How reproducible: 100% Steps to Reproduce: 1. Add an Openstack Platform Director 2. Go to Infrastructure - Nodes 3. Click on one of the nodes 4. Check the Power button Actual results: The Power button is active but shows an empty list of actions. Expected results: The Power button is disabled. Additional info: How the power button currently shows: See attachment. How the power button should show: https://cloud.githubusercontent.com/assets/1737058/11032643/63650046-86dd-11e5-93a7-c69c6ad53073.png
Dan, it seems that the toolbar formating issue that was there is fixed in the last build. What remains is the fact that those buttons do not do anything when clicked. So we should probably disable those buttons. Ladas: can you help me identify the conditions under which the buttons shall be visible/enabled? Shall it be disabled for all OpenStack hosts?
Yes, for now, OpenStack infra hosts doesn't support any action. Though very soon pblaho should add 2 new actions, that we support.
Status update: the reported problem is fixed in current 5.5 What remains is the situation where a list of hosts is displayed and one or more items are selected. What is a general issue with toolbars and display of items of different type described here: https://github.com/ManageIQ/manageiq/issues/5597 As a quick solution we need to display a flash message when an action is fired that is not allowed for the particular host.
upstream PR: https://github.com/ManageIQ/manageiq/pull/5636
Power button is disabled.tested 5.6.0.8-rc1
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/RHBA-2016:1348