[
https://issues.apache.org/jira/browse/AMBARI-13450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960853#comment-14960853
]
Hadoop QA commented on AMBARI-13450:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12767049/BootStrap_via_different_SSH_port_number1.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3985//console
This message is automatically generated.
> Bootstrap Cluster via different SSH Port Number
> -----------------------------------------------
>
> Key: AMBARI-13450
> URL: https://issues.apache.org/jira/browse/AMBARI-13450
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server, ambari-web
> Affects Versions: 2.1.0
> Reporter: Selim Ozcan
> Labels: features, patch
> Attachments: BootStrap_via_different_SSH_port_number1.patch
>
>
> For the time being, bootstrapping cluster is done via default port number 22
> for SSH and SCP protocols without an option to specify the port number.
> There was a need to bootstrap cluster via different port number at the
> laboratory which I work at but Apache Ambari didn't have that option so we
> add that functionality. It still uses the default port number 22 unless you
> change it at Installer Wizard Step 2.
> A Textfieldview (default written value '22' SSH Port number ) added to
> installer wizard step 2, same as specifying ssh user field which is default
> to 'root' user, to take the SSH port input from user. After that, Port number
> is transferred to bootstrapping functions along with sshUser value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
