ambari-issues mailing list archives

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


Hadoop QA commented on AMBARI-17188:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results:
Console output:

This message is automatically generated.

> Ambari upgrade from 2.2.2 to 2.4.0 fails if cluster name was changed
> --------------------------------------------------------------------
>                 Key: AMBARI-17188
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-upgrade
>    Affects Versions: 2.4.0
>            Reporter: Gaurav Nagar
>            Assignee: Gaurav Nagar
>            Priority: Critical
>             Fix For: 2.4.0
>         Attachments: AMBARI-17188_branch-2.4.patch
> STR:
> 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:
> {code}
> 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
> {code}
> Error occurs in UpgradeCatalog240.upgradeCapSchedulerView(), here :
> {code}
> clusterEntity.setPassword(new DefaultMasker().unmask(propertyMap.get("ambari.server.password")));
> {code}
> 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