[AMBARI-15894] After adding support for real jdbc jar names, verify the post Ambari upgrade nothing breaks

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.4.0
• Fix Version/s: 2.4.0
• Component/s: ambari-server
• Assignee: Vitaly Brodetskyi
• Reporter: Vitaly Brodetskyi
• Created: 14/Apr/16 18:36
• Updated: 15/Apr/16 13:45
• Resolved: 15/Apr/16 10:27

Description

Lets think through the upgrade scenario again:
Prior to upgrade we know of hard-coded names and the system is in working state
During upgrade, lets pre-populate the ambari.properties file with the old hard-coded values (think of them as the real names as thats what we know)
If user wants to use real name, they can call ambari-server setup ...
Net goal is to not have user do anything post Ambari upgrade.

Issue Links

• links to: review request