ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14668) Kerberos specifical properties reverted during secured cluster deploy via blueprint
Date Fri, 15 Jan 2016 00:56:39 GMT

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

Hadoop QA commented on AMBARI-14668:
------------------------------------

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

This message is automatically generated.

> Kerberos specifical properties reverted during secured cluster deploy via blueprint
> -----------------------------------------------------------------------------------
>
>                 Key: AMBARI-14668
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14668
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.2.1
>
>         Attachments: AMBARI-14668.patch
>
>
> 1) Deploy cluster with HDFS,YARN,Oozie, Storm,Zookeeper.
> 2) Enable security.
> 3) Customize some properties: hadoop.proxyuser.yarn.hosts, hadoop.proxyuser.HTTP.groups,
oozie.authentication.type, yarn.timeline-service.http-authentication.type.
> 4) Export blueprint config. Check that customized properties are correct in exported
config.
> 5) Deploy kerberized cluster via blueprints.
> 6) Check that after deploy customized properties are the same as they were set during
customization.
> Result: customized properties were reverted. Looks like during BP deploy, we are just
updating all kerberos properties with values from kerberos.json from related service



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

Mime
View raw message