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

Repository 2: RepositoryAuditTask can be blocked by any task that is running against a different repository

    Details

    • Type: Bug
    • Status: New
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: 2.14.16
    • Fix Version/s: None
    • Component/s: Firewall, Scheduled Tasks
    • Labels:
    • Notability:
      3

      Description

      Create the following Maven group repository hierarchy:

      Maven Group Repo - A

      • Maven hosted repo with version policy SNAPSHOT - B
      • Maven Proxy repo to Central - C, containing lots of artifacts already cached

      1. Set com.sonatype.nexus.clm logger to DEBUG
      2. Connect repo to a running IQ Server.
      3. In Repo, run a long running Snapshot remover task ( repo contains lots of snapshots ) called "B cleanup" against the B repository
      4. While snapshot remover is still running, enable IQ: Audit and Quarantine against C repository - repository audit only, no quarantine

      Observe that the background audit task is blocked by the Snapshot remover task with a log statement similar to:

      *TASK com.sonatype.nexus.clm.internal.RepositoryAuditTask - Task B cleanup is already running and is conflicting with task RepositoryAuditTask
      

      Also observe that in the Repositories list, for Proxy repo B, one will see a message "Audit in progress" that never seems to clear itself and provide the expected link to the audit report.

      When navigating to the expected report location in IQ Server, vie Root Organization -> Repositories, the link to the report can be located, and opened, but the report never shows any components that were already present in the Central repo.

      Recall that a repository audit task is only relevant for OSS RELEASE components in Proxy repositories and the task cannot be run or provide effective results against hosted repos and SNAPSHOT versioned artifacts.

      Expected

      Repository Audit task should not be blocked when:

      • another task is running against ANY other hosted repository
      • another task is running against a different proxy repository than the audit task is configured on

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            plynch Peter Lynch
            Last Updated By:
            Hajime Osako Hajime Osako
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Date of First Response:

                tigCommentSecurity.panel-title