[jira] [Comment Edited] (AMBARI-20402) Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page

["Sangeeta Ravindran (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-20402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922982#comment-15922982 ] 

Sangeeta Ravindran edited comment on AMBARI-20402 at 3/13/17 9:34 PM:
----------------------------------------------------------------------

Failure in Jenkins build is unrelated to the fix.
Failure occurs in ambari-admin project:

Additional error details:
fatal: unable to access 'https://github.com/lodash/lodash.git/': gnutls_handshake() failed: A TLS packet with unexpected length was received.
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
	at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)


was (Author: sangeetar):
Committed to 2.5 as 
commit 819d4f25339476622ffe73dd64acb85e24b52969
Author: Sangeeta Ravindran <sa...@apache.org>
Date:   Mon Mar 13 11:56:04 2017 -0700

AMBARI-20402: Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page (sangeetar)


> Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-20402
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20402
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.5.0
>            Reporter: Sangeeta Ravindran
>            Assignee: Sangeeta Ravindran
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-20402.patch, AssignSlavesAndClients_AfterChanges.jpg, AssignSlavesAndClients_BeforeChanges.jpg
>
>
> 1. On a multi-node cluster (for e.g. 5-node cluster), run the ambari install wizard.
> 2. Do not change defaults and navigate to Step 6 (Assign Slaves and Clients). 
> 3. The recommended configuration does not seem to be place the components well. For e.g., DataNodes are recommended on all 5 nodes. (see AssignSlavesAndClients_BeforeChanges.jpg).
> 4. Navigate back to Step 5 (Assign Masters). Make a change. For e.g. move the Atlas Metadata Server to a different host. Next, change it back to the original host so that in effect nothing has changed.
> 5. Now move to Step 6 again and see that the configuration has changed and seems more in line with best practices although effectively nothing has changed in the Assign Masters page. (see AssignSlavesAndClients_AfterChanges.jpg)



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