Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-13999

Upgrades should not rely on a specific username/group


    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Installer


      Upgrades should not rely on a specific username/group.

      When upgrading Artifactory via yum/debian/rpm/deb, the upgrade script will ALWAYS try to create the artifactory group and user. This is the case even when the user/group running Artifactory has been set to a different username/group.

      To reproduce

      1. Perform a YUM installation of an older version of Artifactory (say 4.12.2)
      2. Create a new user and group with a different name (say 'paco')
      3. Change the ownership of all the relevant folders to the new user/group and set the new user in the default file
      4. Start Artifactory and confirm the new user is being used
      5. Delete user and group artifactory
      6. Perform an upgrade (yum upgrade artifactory)
      7. Observe the error

      Group artifactory doesn't exist. Creating ...
      groupadd: GID '500' already exists
      error: %pre(jfrog-artifactory-pro-4.14.0-40293.noarch) scriptlet failed, exit status 4
      error:   install: %pre scriptlet failed (2), skipping jfrog-artifactory-pro-4.14.0-40293
      jfrog-artifactory-pro-4.12.2-40261.noarch was supposed to be removed but is not!




            • Assignee:
              anastasiag Anastasia Grinman
              krihelis Shlomi Kriheli
              Assigned QA:
              Mor Iluz (Inactive)
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created: