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

Hudson commented on AMBARI-19296:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6315 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6315/])
AMBARI-19296. When adding service, custom core-site properties get 
(dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d84aa3bcb184db60e8d1a68429e1c7abb3fa3646])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.1/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py


> When adding service, custom core-site properties get reverted back
> ------------------------------------------------------------------
>
>                 Key: AMBARI-19296
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19296
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.0
>            Reporter: Eugene Chekanskiy
>            Assignee: Eugene Chekanskiy
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19296-branch-2.5.patch, AMBARI-19296.patch
>
>
> PROBLEM:  When adding a new services like Kafka, Flume, core-site properties 
> reverted.
> The below parameter vaues are changed. 
> hadoop.proxyuser.HTTP.groups 
> hadoop.proxyuser.HTTP.hosts 
> hadoop.proxyuser.knox.groups 
> hadoop.proxyuser.knox.hosts 
> hadoop.proxyuser.HTTP.groups default users we want * it changes to users 
> hadoop.proxyuser.HTTP.hosts it should be three namenodes but it reverts to 
> name2 



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

Reply via email to