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

Group repository can have members removed inadvertently after update which includes a not existing member

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.14.3
    • Fix Version/s: 2.14.9
    • Component/s: Repository
    • Labels:

      Description

      Following these steps it was found that a group repository could have all its members removed:

      • Create a group repository with some member repositories.
      • PUT an update request for the group repository that contains a member that doesn't exist. To reproduce, the update request must have the ordering of the non-existant member before other existing members. The existing members that are after are the ones that will be removed.
      • Modify and save any other repository (doesn't have to be in the group).
      • Your group repository will now have lost the members following the non-existant one.

      This seems boundless so could be 1 or thousands of repositories affected.

        Attachments

          Activity

            People

            Assignee:
            jtom Joe Tom
            Reporter:
            jtom Joe Tom
            Last Updated By:
            Peter Lynch
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                tigCommentSecurity.panel-title