You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/08/01 05:53:00 UTC
[jira] [Commented] (AMBARI-24283) DB consistency warning due to
config group without service name
[ https://issues.apache.org/jira/browse/AMBARI-24283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564776#comment-16564776 ]
Hudson commented on AMBARI-24283:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #94 (See [https://builds.apache.org/job/Ambari-branch-2.7/94/])
AMBARI-24283 - DB consistency warning due to config group without (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=1c25b1019b8eaa6b03882ae4ee7bdd99b9ae1d5d])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog271.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog271Test.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelperTest.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java
> DB consistency warning due to config group without service name
> ---------------------------------------------------------------
>
> Key: AMBARI-24283
> URL: https://issues.apache.org/jira/browse/AMBARI-24283
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.6.0
> Reporter: Doroszlai, Attila
> Assignee: Krisztian Kasa
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 7.5h
> Remaining Estimate: 0h
>
> STR:
> 1. Deploy ZooKeeper with Ambari 2.5.2
> 2. Create config group on UI
> 3. Upgrade to Ambari 2.6.x
> {noformat}
> group_id | group_name | tag | service_name
> ----------+------------+-----------+--------------
> 3 | asdf | ZOOKEEPER |
> {noformat}
> Result: DB consistency check during startup after the upgrade produces false positive warning about the config group
> {noformat}
> WARN - You have config groups present in the database with no corresponding service found, [(ConfigGroup, Service) => ( asdf, null )]. Run --auto-fix-database to fix this automatically.
> {noformat}
> Following the instructions ({{--auto-fix-database}}) leads to deleting the config group.
> This check was added for the case where the service the config group belongs to was deleted from the cluster.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)