[
https://issues.apache.org/jira/browse/AMBARI-18216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15428498#comment-15428498
]
Hadoop QA commented on AMBARI-18216:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12824600/AMBARI-18216.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8469//console
This message is automatically generated.
> Both NameNodes reporting version mismatches before Finalizing RU
> ----------------------------------------------------------------
>
> Key: AMBARI-18216
> URL: https://issues.apache.org/jira/browse/AMBARI-18216
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Nate Cole
> Assignee: Nate Cole
> Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18216.patch
>
>
> When doing RU on a secured cluster, the MasterHostResolver class is failing
> the lookup of JMX. Ambari's SSL configuration must be used just like metrics
> do.
> Also adding some logging, and making sure that if we have 2 confirmed NN,
> that we are always picking one to be the active and one to be the standby.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
