[AMBARI-21626] Configs For Target Stack Are Not Created During Upgrade

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.6.0
• Epic Link: Ambari: Patch Upgrades
• Assignee: Jonathan Hurley
• Reporter: Jonathan Hurley
• Created: 01/Aug/17 21:48
• Updated: 02/Aug/17 16:22
• Resolved: 02/Aug/17 15:04

Description

During an upgrade from HDP 2.5 to HDP 2.6, the new configurations are not created in HDP 2.6 - they're created in HDP 2.5 which causes services to fail on restart.

STR:

• Create an HDP 2.5 cluster with ZK + HDFS
• Do an EU to HDP 2.6

The EU will fail right after the "move stack version" step.

It looks like the bug is in ConfigHelper where it ignores the passed-in StackId and uses the Cluster's stack:

  Config createConfig(Cluster cluster, StackId stackId, AmbariManagementController controller,
      String type, String tag, Map<String, String> properties,
      Map<String, Map<String, String>> propertyAttributes) throws AmbariException {

        ...
    return controller.createConfig(cluster, type, properties, tag, propertyAttributes);
  }

Issue Links

• links to: ReviewBoard