[AMBARI-21940] Ambari schema upgrade from any version older than 2.5.1 fails due to incorrect version check

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.6.0
• Component/s: ambari-server
• Labels: upgrade
• Assignee: Dmitry Lysnichenko
• Reporter: Vivek Sharma
• Created: 12/Sep/17 18:13
• Updated: 14/Sep/17 17:07
• Resolved: 14/Sep/17 16:04

Description

Perform an upgrade from Ambari version older than 2.5.1 (like 2.5.0 or 2.4.x) to 2.6.0

Fails with below error

12 Sep 2017 02:16:35,727  INFO [main] TransactionalLock$LockArea:121 - LockArea HRC_STATUS_CACHE is enabled
12 Sep 2017 02:16:36,091  INFO [main] LockFactory:53 - Lock profiling is disabled
12 Sep 2017 02:16:36,112  INFO [main] SchemaUpgradeHelper:391 - Upgrading schema to target version = 2.6.0.0
12 Sep 2017 02:16:36,115  INFO [main] SchemaUpgradeHelper:400 - Upgrading schema from source version = 2.5.0
12 Sep 2017 02:16:36,118 ERROR [main] SchemaUpgradeHelper:434 - Exception occurred during upgrade, failed
org.apache.ambari.server.AmbariException: Database version does not meet minimal upgrade requirements. Expected version should be not less than 2.5.1, current version is 2.5.0
        at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:405)
12 Sep 2017 02:16:40,419  INFO [main] Configuration:3044 - Reading password from existing file
12 Sep 2017 02:16:40,439  INFO [main] Configuration:3529 - Hosts Mapping File null
12 Sep 2017 02:16:40,439  INFO [main] HostsMap:60 - Using hostsmap file null
12 Sep 2017 02:16:41,290  INFO [main] ControllerModule:221 - Detected MYSQL as the database type from the JDBC URL

Issue Links

• links to: review_request_