You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Antonenko Alexander (JIRA)" <ji...@apache.org> on 2017/05/24 22:36:04 UTC

[jira] [Updated] (AMBARI-21117) Existing hosts state didn't save after host was added

     [ https://issues.apache.org/jira/browse/AMBARI-21117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antonenko Alexander updated AMBARI-21117:
-----------------------------------------
    Status: Patch Available  (was: Open)

> Existing hosts state didn't save after host was added
> -----------------------------------------------------
>
>                 Key: AMBARI-21117
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21117
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.5.1
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>            Priority: Blocker
>             Fix For: 2.5.1
>
>         Attachments: AMBARI-21117.patch
>
>
> Existing hosts state didn't save after host was added. In next test add host wizard stay open.
> When we connect to cluster - automatically redirect on add host wizard. (attached screenshot)
> First step validation passed and host registered successfully. 
> On Review Page, when we clicked Deploy we had popup with error that this host already part of cluster.
> If we cluster wizard and try it again - validation on first step not passed



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)