ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-19296) When adding service, custom core-site properties get reverted back
Date Wed, 28 Dec 2016 14:59:58 GMT

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

Dmitry Lysnichenko updated AMBARI-19296:
----------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed
To https://git-wip-us.apache.org/repos/asf/ambari.git
   cf28b98..ebaa0ea  branch-2.5 -> branch-2.5
   1bfffc0..d84aa3b  trunk -> trunk


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

Mime
View raw message