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

edited Cleanup Policies with Component Age or Component Usage criteria can be improperly applied

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 3.29.1
    • Fix Version/s: 3.29.2
    • Component/s: Cleanup, Scheduled Tasks
    • Environment:
      Linux
      openjdk version "1.8.0_275"
      OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_275-b01)
      OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.275-b01, mixed mode)
    • Release Note:
      Yes

      Description

      Problem

      In NXRM 3.29.1, saving or creating Cleanup Policies with Component Age or Component Usage criteria will save the day values as seconds. The result can be that when these cleanup policies are applied by a running "Admin - Cleanup repositories using their associated policies" task, more components than you intended can get removed by the policy.

      Only version 3.29.1 is affected.

      Solution

      1. Upgrade to version 3.29.2 and newer. New versions will properly save Cleanup Policy day criteria values as days, not seconds, as originally intended.
      2. After upgrading from 3.29.1 to 3.29.2 or greater, review all of your cleanup policy criteria for accurate values specifically in the Component Age and Component Usage Cleanup Criteria. If a cleanup policy was created or edited using 3.29.1 with day criteria values, when opening the policy in 3.29.2 or newer, the value will render as a value of 0 ( zero ). In that case change the value 0 to your desired day value and Save the policy.

      FAQ

      Q: If I am using 3.29.1 and have not created or saved any existing cleanup policies, am I at risk of being affected by this bug?

      A: Improper day values only get applied if your cleanup policies are edited or created while running 3.29.1, and you are using the affected criteria. However remaining on 3.29.1 puts your cleanup policies at risk of being editing and triggering the bug.


      Q: How can I know if I have cleanup policies that were affected when running 3.29.1?

      A: If a cleanup policy was created or edited using 3.29.1 with day criteria values, when opening the policy in 3.29.2 or newer, the value will render as a value of 0 ( zero ). In that case change the value 0 to your desired day value and Save the policy.


      Q: I'm running 3.29.1 and have not upgraded to 3.29.2 or newer and don't want to be affected by this bug. What should I do?

      A: Any 3.29.1 instance is advised to implement the following actions immediately:

      1. Notify all your NXRM administrators to not edit or create Cleanup Policies with Component age or Component Usage criteria.

      2. Temporarily disable cleanup policies:

      1. As an Administrator user, navigate to Administration → System → Tasks.
      2. Select the task of type "Admin - Cleanup repositories using their associated policies". The default task name is "Cleanup service". Click the task Settings tab.
      3. Uncheck the Task enabled checkbox on the Settings tab and click Save.

      3. Temporarily prevent permanent deletion of incorrectly soft-deleted components in file based blob stores:

      1. As an Administrator user, navigate to Administration → System → Tasks.
      2. For each task of type "Admin - Compact blob store". Click the task Settings tab.
      3. Uncheck the Task enabled checkbox on the Settings tab and click Save.

      4. Temporarily prevent permanent deletion of incorrectly soft-deleted components in AWS S3 based blob stores:

      1. As an Administrator user, navigate to Administration → Repository → Blob stores.
      2. For each S3 Blobstore, navigate to the bob store settings page. Change Expiration Days to -1 to disable lifecycle cleanup policies for soft deleted blobs.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ataylor Andrew Taylor
              Reporter:
              tcassidy Tom Cassidy
              Last Updated By:
              Peter Lynch
              Votes:
              1 Vote for this issue
              Watchers:
              15 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title