[
https://issues.apache.org/jira/browse/AMBARI-15254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177127#comment-15177127
]
Hadoop QA commented on AMBARI-15254:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12791039/AMBARI-15254.branch22.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/5693//console
This message is automatically generated.
> Ambari config update does not handle removals properly
> ------------------------------------------------------
>
> Key: AMBARI-15254
> URL: https://issues.apache.org/jira/browse/AMBARI-15254
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: trunk, 2.2.0
> Reporter: Lav Jain
> Assignee: Lav Jain
> Fix For: 2.3.0, 2.2.2
>
> Attachments: AMBARI-15254.branch22.patch, AMBARI-15254.patch
>
>
> ConfigHelper.updateConfigType takes in config_type (e.g. hdfs-site), map of
> updates (key value pairs) and a list of removals (properties).
> The current implementation is skipping the updates to configuration if the
> Map of updates is empty, even if there are properties to be removed.
> This is causing problem during disabling of kerberos for some components
> (like HAWQ) because some config parameters that are present in kerberos.json
> must be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
