[
https://issues.apache.org/jira/browse/AMBARI-14668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102572#comment-15102572
]
Hudson commented on AMBARI-14668:
---------------------------------
SUCCESS: Integrated in Ambari-branch-2.2 #208 (See
[https://builds.apache.org/job/Ambari-branch-2.2/208/])
AMBARI-14668. Kerberos specifical properties reverted during secured
(vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4e50772cffb35a6cf6f8d179899f70ce49c25c38])
*
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
*
ambari-server/src/main/java/org/apache/ambari/server/topology/ClusterConfigurationRequest.java
*
ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterConfigurationRequestTest.java
> 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)