[
https://issues.apache.org/jira/browse/AMBARI-12486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645554#comment-14645554
]
Hadoop QA commented on AMBARI-12486:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12747657/AMBARI-12486.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3492//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3492//console
This message is automatically generated.
> Enabling namenode HA fails when non default ports are used
> ----------------------------------------------------------
>
> Key: AMBARI-12486
> URL: https://issues.apache.org/jira/browse/AMBARI-12486
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-web
> Affects Versions: 2.1.0, trunk
> Reporter: Juanjo Marron
> Assignee: Juanjo Marron
> Fix For: 2.1.1
>
> Attachments: AMBARI-12486.patch
>
>
> Enabling HA code may not read correct properties.
> When HDFS and ZOOKEEPER ports are changed (different than default values ZK:
> 2181 and HDFS: 8020,50070,50470), HA wizard menus is still showing the ones
> by default and HA namenode fails with connection errors.
> Checked the source code for the Step 3 in namenode HA wizard
> (ambari-web/app/controllers/main/admin/highAvailability/nameNode/step3_controller.js)
> The node address is looked from the configuration but ports hardcoded instead
> of the new once modified on the installation wizard, ex:
> ...
> this.setConfigInitialValue(config,'qjournal://' + journalNodeHosts[0] +
> ':8485;' + journalNodeHosts[1] + ':8485;' + journalNodeHosts[2] + ':8485/' +
> nameServiceId);
> this.setConfigInitialValue(config,zooKeeperHosts[0] + ':2181,' +
> zooKeeperHosts[1] + ':2181,' + zooKeeperHosts[2] + ':2181');
> ...
> This is a bug that should be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
