[AMBARI-24283] DB consistency warning due to config group without service name

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Component/s: ambari-server
• Labels: pull-request-available
• Assignee: Krisztian Kasa
• Reporter: Attila Doroszlai
• Created: 11/Jul/18 19:48
• Updated: 01/Aug/18 05:54
• Resolved: 01/Aug/18 05:54

Description

STR:

1. Deploy ZooKeeper with Ambari 2.5.2
2. Create config group on UI
3. Upgrade to Ambari 2.6.x

 group_id | group_name |    tag    | service_name
----------+------------+-----------+--------------
        3 | asdf       | ZOOKEEPER |

Result: DB consistency check during startup after the upgrade produces false positive warning about the config group

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.

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.

Issue Links

• links to: GitHub Pull Request #1751
• links to: GitHub Pull Request #1876
• links to: GitHub Pull Request #1915
• links to: GitHub Pull Request #1928