Details
-
Bug
-
Resolution: Fixed
-
Medium
-
3.12.1, 3.13.1
-
3.12
-
Description
Steps to reproduce:
- import a backup to a currently running instance and specify a new index directory
- JIRA will create the new directory, populate the index, and then delete the old index comments and issues directories. The plugins directory remains.
In the logs is evidence that JIRA is attempting to delete
(/tmp/jira/ is the original index)2008-11-11 17:16:17,317 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /tmp/jira/plugins
This is especially concerning for environments where production and development staging instances are hosted on the same box
Attachments
Issue Links
- is related to
-
JRASERVER-15765 XML import from JIRA 3.11 to 3.13 failing on windows
- Closed