You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/02/06 01:26:39 UTC
[jira] [Commented] (AMBARI-14948) Config consistency checker
[ https://issues.apache.org/jira/browse/AMBARI-14948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135337#comment-15135337 ]
Hadoop QA commented on AMBARI-14948:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12786573/AMBARI-14948.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/5241//console
This message is automatically generated.
> Config consistency checker
> --------------------------
>
> Key: AMBARI-14948
> URL: https://issues.apache.org/jira/browse/AMBARI-14948
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.2
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14948.patch
>
>
> Command line utility to find inconsistencies in configs
> Services without configs
> Configs without services
> relationship between clusterconfig, serviceconfigmapping, and clusterconfigmapping
> Do outter joins and find missing configs
> At least one should be selected for config type, compare known config types vs expected in the stack, versions are incremental
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)