[ 
https://issues.apache.org/jira/browse/AMBARI-20358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15901261#comment-15901261
 ] 

Hudson commented on AMBARI-20358:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6974 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6974/])
AMBARI-20358. NPE during Ambari server schema upgrade while updating (rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f39207a53df94433ca0ac39ffde6f5fb9f7994c6])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java


> NPE during Ambari server schema upgrade while updating hbase_master_cpu alert 
> definition
> ----------------------------------------------------------------------------------------
>
>                 Key: AMBARI-20358
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20358
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Blocker
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-20358_branch-2.5_01.patch, 
> AMBARI-20358_trunk_01.patch
>
>
> Probably caused by this commit: 
> https://github.com/hortonworks/ambari/commit/6be4a18dd00f9d23d63410b748d67c952a6240c8
> *STR*
> # Deploy HDP-2.3.6 with Ambari-2.2.2.0
> # Upgrade Ambari to 2.5.0.1-13 (hash: 
> 52b820b0c899a0246061c51245aca231c63583d7) - this includes executing 'yum 
> upgrade ambari-server' followed by 'ambari-server upgrade'
> *Result*
> Error during DB schema upgrade
> {code}
> 08 Mar 2017 04:52:22,059  INFO [main] AbstractUpgradeCatalog:609 - cluster 
> 'cl1' changed by: 'ambari-upgrade'; type='ranger-kafka-security' 
> tag='version1488948741867' from='version1488942647954'
> 08 Mar 2017 04:52:23,469  INFO [main] UpgradeCatalog250:214 - Updating alert 
> definition hbase_master_cpu in cluster 2
> 08 Mar 2017 04:52:23,471 ERROR [main] SchemaUpgradeHelper:239 - Upgrade 
> failed.
> java.lang.NullPointerException
>         at 
> org.apache.ambari.server.upgrade.UpgradeCatalog250.fixHBaseMasterCPUUtilizationAlertDefinition(UpgradeCatalog250.java:229)
>         at 
> org.apache.ambari.server.upgrade.UpgradeCatalog250.executeDMLUpdates(UpgradeCatalog250.java:197)
>         at 
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:952)
>         at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
>         at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> 08 Mar 2017 04:52:23,474 ERROR [main] SchemaUpgradeHelper:443 - Exception 
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException
>         at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
>         at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> Caused by: java.lang.NullPointerException
>         at 
> org.apache.ambari.server.upgrade.UpgradeCatalog250.fixHBaseMasterCPUUtilizationAlertDefinition(UpgradeCatalog250.java:229)
>         at 
> org.apache.ambari.server.upgrade.UpgradeCatalog250.executeDMLUpdates(UpgradeCatalog250.java:197)
>         at 
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:952)
>         at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
>         ... 1 more
> 08 Mar 2017 04:52:27,829  INFO [main] Configuration:2906 - Reading password 
> from existing file
> 08 Mar 2017 04:52:27,863  INFO [main] Configuration:3382 - Hosts Mapping File 
> null
> 08 Mar 2017 04:52:27,864  INFO [main] HostsMap:60 - Using hostsmap file null
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to