ambari-dev mailing list archives

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

     [ https://issues.apache.org/jira/browse/AMBARI-14668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vitaly Brodetskyi updated AMBARI-14668:
---------------------------------------
    Attachment:     (was: AMBARI-14668.patch)

> 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
>
>
> 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