You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2015/12/03 23:16:11 UTC
[jira] [Updated] (AMBARI-12949) Downgrade fails with err: 500
status code received on POST method for API:
/api/vi/clusters/mycluster/upgrades
[ https://issues.apache.org/jira/browse/AMBARI-12949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yusaku Sako updated AMBARI-12949:
---------------------------------
Fix Version/s: (was: trunk)
2.3.0
> Downgrade fails with err: 500 status code received on POST method for API: /api/vi/clusters/mycluster/upgrades
> --------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-12949
> URL: https://issues.apache.org/jira/browse/AMBARI-12949
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Di Li
> Assignee: Di Li
> Priority: Critical
> Fix For: 2.3.0
>
> Attachments: AMBARI-12949.patch
>
>
> I have a 4 node HDP 2.2 cluster where I created a configuration group to apply customized oozie_heap_size to the Oozie server and one of the Oozie client. I was able to rolling upgrade the cluster to HDP 2.3, but when I clicked Downgrade button on the Finalize step. The Ambari UI immediately threw error message "500 status code received on POST method for API: /api/vi/clusters/mycluster/upgrades"
> Checking the Ambari server log, it reported a nullpointer error when trying to load the designed configurations
> Aug 30, 2015 11:01:07 PM com.sun.jersey.spi.container.ContainerResponse mapMappableContainerException
> SEVERE: The RuntimeException could not be mapped to a response, re-throwing to the HTTP container
> java.lang.NullPointerException
> at org.apache.ambari.server.state.host.HostImpl.getDesiredHostConfigs(HostImpl.java:1349)
> Digging around in the database, I saw that the oozie-env (where I had a configuration group) had no version_tag set with "selected" as 1.
> Manually setting the version1 row to have selected = 1, restart server and then I was able to run downgrade. However, the downgrade failed to mark itself as finished, and my Ambari WEB UI remained in this "Downgrade:Aborted" state and I can't restart components anymore (as in most of the UI features are disabled as the UI still thinks it's in the middle of an downgrade).
> ambari=> select * from clusterconfigmapping where type_name = 'oozie-env';
> cluster_id | type_name | version_tag | create_timestamp | selected | user_name
> ------------+-----------+----------------------+------------------+----------+----------------
> 2 | oozie-env | version1 | 1441033897383 | 0 | admin
> 2 | oozie-env | version1441037586550 | 1441037586592 | 0 | ambari-upgrade
> 2 | oozie-env | version1441039514060 | 1441039516239 | 0 | admin
> (3 rows)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)