[jira] [Created] (AMBARI-7369) Clients in INIT or INSTALL FAILED state should have an menu action for installation

["Antonenko Alexander (JIRA)" <ji...@apache.org>]

Antonenko Alexander created AMBARI-7369:
-------------------------------------------

             Summary: Clients in INIT or INSTALL FAILED state should have an menu action for installation
                 Key: AMBARI-7369
                 URL: https://issues.apache.org/jira/browse/AMBARI-7369
             Project: Ambari
          Issue Type: Bug
          Components: ambari-client
    Affects Versions: 1.7.0
            Reporter: Antonenko Alexander
            Assignee: Antonenko Alexander
             Fix For: 1.7.0
         Attachments: Screen Shot 2014-08-05 at 5.35.38 PM.png

A client host component can either be in INIT, INSTALLED or INSTALL_FAILED state.
If a client host component exists irrespective of whatever state, it is shown in the list of installed clients on host component page. (Please see the snapshot)

If for some reason client is in INIT state or INSTALLED_FAILED state still it shows up in the list of installed client and thereafter there is no way from UI to install the client component

web-ui does have a specific status icon for slave/master components in INSTALL_FAILED and INIT state but this is not shown for client components. 

# As a resolution to this ticket, we should show the correct status icon before the client component name in the list of clients when they are in INIT or INSTALL_FAILED state.
# When any of the client component in the list of clients is in INIT or INSTALL_FAILED state then the overall current state of the clients should be *Pending installation or Install Failed* respectively and the dropdown menu action should also have *Install clients* action triggering which installs the INIT/INSTALL_FAILED clients.
# If all clients are in installed state then the overall state of the clients is *Installed* and the menu action has only refresh configs command enabled/disabled depending upon stale configs (this is usual scenario supported as of today) 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)