[
https://issues.apache.org/jira/browse/AMBARI-18305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-18305:
----------------------------------------
Status: Patch Available (was: Open)
> (2.5.0 fix) Ambari server upgrade script deletes all .pyc files
> ---------------------------------------------------------------
>
> Key: AMBARI-18305
> URL: https://issues.apache.org/jira/browse/AMBARI-18305
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18305.patch
>
>
> From customer case:
> We are trying upgrade Ambari from 2.2.2 to Ambari 2.4 with the latest
> packages (1226).
> https://issues.apache.org/jira/browse/AMBARI-15947 - "Upgrading Ambari should
> delete any pyc files"
> The patch contains the following two lines
> {code}
> AMBARI_SERVER="${ROOT}/usr/lib/python2.6/site-packages/ambari_server"
> find $AMBARI_SEVER/ -name *.pyc -exec rm {} \;
> {code}
> The AMBARI_SEVER typo basically executes "find / -name *.pyc -exec rm {} \;"
> on the root directory and deletes ALL pyc files from the ambari server
> machine.
> This looks like a bug in the latest Ambari package we released yesterday.
> Considering the command has both "rm" and "*" in the same line, lets see if
> we can use a safer strategy such as changing the CWD and then deleting files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
