You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/06/25 19:34:05 UTC

[jira] [Commented] (AMBARI-12146) Ambari JAAS configuration removed after 2.0.1 to 2.1 upgrade

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

Hadoop QA commented on AMBARI-12146:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12741897/AMBARI-12146.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/3266//console

This message is automatically generated.

> Ambari JAAS configuration removed after 2.0.1 to 2.1 upgrade
> ------------------------------------------------------------
>
>                 Key: AMBARI-12146
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12146
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-12146.patch
>
>
> After upgrading from Ambari 2.0.1 with SPNEGO configured, and JAAS configured through ambari-server setup-security to 2.1.0-1158, after the upgrade the JAAS settings are not retained so there are multiple UI issues as SPNEGO is in use and prevents Ambari from accessing JMX endpoints without authentication:
> *Steps to reproduce*
> * Install Ambari 2.0.1 with HDP 2.2.6
> * Configure SPNEGO
> * Configure Ambari's JAAS using ambari-server setup-security
> * Upgrade to Ambari 2.1.0-1158
> * Start services
> * Notice the JAAS settings are not retained and HDFS Summary screen is not accurate



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)