[
https://issues.apache.org/jira/browse/AMBARI-21784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16138147#comment-16138147
]
Hadoop QA commented on AMBARI-21784:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12883242/AMBARI-21784.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/12046//console
This message is automatically generated.
> Ambari server logs consistency check warning after service delete with
> ConfigGroup present
> ------------------------------------------------------------------------------------------
>
> Key: AMBARI-21784
> URL: https://issues.apache.org/jira/browse/AMBARI-21784
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 2.6.0
>
> Attachments: AMBARI-21784.patch
>
>
> Ambari server log is constantly populated with 'Config inconsistency exists:
> unknown configType=solr-site' even after Solr deletion due to existence of
> config group.
> {code}
> 22 Aug 2017 19:00:20,094 ERROR [ambari-hearbeat-monitor] HostImpl:1085 -
> Config inconsistency exists: unknown configType=solr-site
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
