[
https://issues.apache.org/jira/browse/AMBARI-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745655#comment-13745655
]
Sumit Mohanty commented on AMBARI-2968:
---------------------------------------
*Work-around*
* Get the current version of the stack deployed
** Through API - http://<ambari-server>:8080/api/v1/clusters/<cluster name> -
see value Clusters/version
*** You will see HDP-1.2.0 or HDP-1.2.1 or HDP-1.3.0, etc.
*** Record this value
* Go to the host where ambari server is hosted
* Stop ambari-server (ambari-server stop)
* Replace file
/var/lib/ambari-server/resources/upgrade/dml/Ambari-DML-Postgres-UPGRADE_STACK.sql
with the attached file
* Upgrade stack version - call "ambari-server upgradestack <HDP stack name as
recorded earlier>" (e.g. ambari-server upgradestack HDP-1.3.2)
* Start ambari-server (ambari-server start)
> Configuration update fails after upgrade
> ----------------------------------------
>
> Key: AMBARI-2968
> URL: https://issues.apache.org/jira/browse/AMBARI-2968
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.2.5
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Fix For: 1.2.5
>
> Attachments: AMBARI-2968.patch, Ambari-DML-Postgres-UPGRADE_STACK.sql
>
>
> After Ambari is upgraded it is not possible to change configurations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
