Removing attachment versions with AttachmentManager results in unexpected warning

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: 10.0.1, 9.5.4
    • Component/s: Content - Attachments
    • None
    • Severity 3 - Minor

      Issue Summary

      When using the methods AttachmentManager.removeAttachmentVersionFromServer or AttachmentService.removeAttachmentVersion in a Confluence DC app, the targeted attachment versions are deleted as expected. However, WARN log entries are generated even when other versions of the attachment still exist. This behavior is unexpected, as these methods are intended to remove only specific versions, not the entire attachment.

      Steps to Reproduce

      1. In Confluence DC, create an attachment with at least two versions.
      2. In an app, use either AttachmentManager.removeAttachmentVersionFromServer or AttachmentService.removeAttachmentVersion to delete the oldest version, leaving at least one newer version.
      3. Observe the application logs.

      Expected Results

      No warnings are logged.

      Actual Results

      The following messages can be seen in the atlassian-confluence.log file:

      WARN [com.atlassian.confluence.impl.pages.attachments.filesystem.ContentDirectoryStructureAttachmentDataFileSystemV004]: Failed to delete file for version 2 of attachment 1111111:
      WARN [com.atlassian.confluence.plugins.synchrony.service.AbstractSynchronyManager]: Duplicated Rev has detected by Synchrony
      

      These WARN logs appear as long as any version of the attachment remains.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            Bernardo Andreeti
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: