[
https://issues.apache.org/jira/browse/AMBARI-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097508#comment-14097508
]
Jaimin D Jetly commented on AMBARI-6862:
----------------------------------------
[~screeley],
This is a front-end issue. Ambari-web renders a default of one host for
installing all client packges on *Assign Slaves and Clients* page
As of now the logic for "default host selection for installing client" while
rendering *Assign slaves and Clients* page is the first datanode host. Earlier
there was a check if datanode is not installed then don't check the datanode
host which was removed in 1.7.0 refactoring work. This leaded to this bug.
I propose to change this logic for "default host selection for installing
client" to select first non-master component. This removes the service (HDFS)
dependent logic.
> Assign Slaves screen - step6 of installer is blank when 2.1.GlusterFS stack
> is used
> -----------------------------------------------------------------------------------
>
> Key: AMBARI-6862
> URL: https://issues.apache.org/jira/browse/AMBARI-6862
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 1.7.0
> Reporter: Scott Creeley
> Assignee: Scott Creeley
> Fix For: 1.7.0
>
>
> assign Slaves screen - step6 of installer is blank when 2.1.GlusterFS stack
> is used for trunk
--
This message was sent by Atlassian JIRA
(v6.2#6252)
