[AMBARI-17604] Ambari server start fails after upgrade due to missing atlas-application configs

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.4.0
• Assignee: Andrew Onischuk
• Reporter: Andrew Onischuk
• Created: 07/Jul/16 11:06
• Updated: 07/Jul/16 13:56
• Resolved: 07/Jul/16 12:15

Description

Likely caused by fix AMBARI-17573

*Steps*

1. Deploy HDP-2.3.4.0 with Ambari 2.2.0.0
2. Upgrade Ambari to 2.4.0.0
3. Run ambari-server start

*Result*
Failed with below error:

ambari-server start
Using python /usr/bin/python
Starting ambari-server
Ambari Server running with administrator privileges.
Organizing resource files at /var/lib/ambari-server/resources...
Ambari database consistency check started...
DB configs consistency check failed. Run "ambari-server start -skip-database-check" to skip. If you use this "-skip-database-check" option, do not make any changes to your cluster topology or perform a cluster upgrade until you correct the database consistency issues. See "/var/log/ambari-server/ambari-server-check-database.log" for more details on the consistency issues.
Ambari database consistency check finished

Log entry:

2016-07-07 06:33:04,252 INFO - ******************************* Check database started *******************************
2016-07-07 06:33:08,700 INFO - Checking for configs not mapped to any cluster
2016-07-07 06:33:08,802 INFO - Checking for configs selected more than once
2016-07-07 06:33:08,808 INFO - Checking for hosts without state
2016-07-07 06:33:08,809 INFO - Checking host component states count equals host component desired states count
2016-07-07 06:33:08,814 INFO - Checking services and their configs
2016-07-07 06:33:11,214 ERROR - Required config(s): falcon-atlas-application.properties is(are) not available for service FALCON with service config version 5 in cluster cl1
2016-07-07 06:33:11,215 ERROR - Required config(s): hive-atlas-application.properties is(are) not available for service HIVE with service config version 7 in cluster cl1
2016-07-07 06:33:11,674 INFO - ******************************* Check database completed *******************************

**Solution:**

There is the same kind of situation with Ranger configs. In the case of Ranger configs we just add them on upgrade even if the service they are for does not exist.
So implementing the same kind of solution here.

Issue Links

• links to: ReviewBoard