Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-26933

Defective error handling when deleting non-empty File-BlobStore

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.30.0
    • Fix Version/s: None
    • Component/s: Blobstore
    • Labels:
      None

      Description

      When deleting a non-empty File BlobStore it gets removed from the UI and database but the data remains on the filesystem. There is no information about this fact despite in the log.
      The user believes that the deletion was successful but the disk-space is still blocked.
      This can lead to outages caused by out of disk space conditions.

      Also using the Rest API returns a (false) positive response code.

      IMHO even when the error handling will be enhanced, there should be a way to forcely delete non-empty blob stores. Removing all components prior to a blob store deletion would be a real time consumenting task.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            catsem Christian Schmitt
            Last Updated By:
            Joe Tom Joe Tom
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Date of First Response:

                tigCommentSecurity.panel-title