ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gaurav Nagar (JIRA)" <>
Subject [jira] [Created] (AMBARI-17188) Ambari upgrade from 2.2.2 to 2.4.0 fails if cluster name was changed
Date Mon, 13 Jun 2016 09:28:21 GMT
Gaurav Nagar created AMBARI-17188:

             Summary: Ambari upgrade from 2.2.2 to 2.4.0 fails if cluster name was changed
                 Key: AMBARI-17188
             Project: Ambari
          Issue Type: Bug
          Components: ambari-upgrade
    Affects Versions: 2.4.0
            Reporter: Gaurav Nagar
            Assignee: Gaurav Nagar
             Fix For: 2.4.0

1) Install ambari 2.2.2 (with YARN)
2) After cluster will be deployed, change cluster name
3) try to upgrade ambari to 2.4.0 version

During upgrade you will get this issue:
Error output from schema upgrade command:
Exception in thread "main" org.apache.ambari.server.AmbariException
        at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(
        at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(
Caused by: java.lang.NullPointerException
        at java.lang.String.<init>(
        at org.apache.ambari.server.view.DefaultMasker.unmask(
        at org.apache.ambari.server.upgrade.UpgradeCatalog240.upgradeCapSchedulerView(
        at org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDMLUpdates(
        at org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(
        at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(
        ... 1 more
Error occurs in UpgradeCatalog240.upgradeCapSchedulerView(), here :
clusterEntity.setPassword(new DefaultMasker().unmask(propertyMap.get("ambari.server.password")));
because all properties in {{propertyMap}} has null value.
In general this method "upgradeCapSchedulerView" was added to upgrade CUSTOM capacity scheduler
view to Remote but "if" construction is not complete. Because when we are doing cluster name
update, {{cluster_handle}} column will not be updated correctly(for ambari 2.2.2). So later
during upgrade when you changing {{cluster_name}} from string to int(cluster id) nothing will
be set in this column. 

This message was sent by Atlassian JIRA

View raw message