You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/10/03 22:07:34 UTC
[jira] [Commented] (AMBARI-7637) Save overwritten custom stacks
before upgrade.
[ https://issues.apache.org/jira/browse/AMBARI-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158452#comment-14158452 ]
Hudson commented on AMBARI-7637:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #476 (See [https://builds.apache.org/job/Ambari-trunk-Commit/476/])
AMBARI-7637. Save overwritten custom stacks before upgrade. (aonishuk) (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c2726070aaa3f0b9ad24001be91b6953f3fbc761)
* ambari-server/src/main/package/rpm/preinstall.sh
* ambari-server/src/main/package/deb/control/preinst
> Save overwritten custom stacks before upgrade.
> ----------------------------------------------
>
> Key: AMBARI-7637
> URL: https://issues.apache.org/jira/browse/AMBARI-7637
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 1.7.0
>
>
> If the customer makes changes to our stack script they get erased after
> upgrade, we should do a backup of stacks folder once upgrading
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)