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

Artifactory should NOT regenerate Access files and communication.key when failing to extract an existing bootstrap bundle

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 5.2.1, 5.3.2
    • Fix Version/s: 5.7.0
    • Component/s: None
    • Labels:
      None

      Description

      If one of the following conditions apply, Artifactory will ignore the bootstrap.bundle.tar.gz during startup:

      1.$ARTIFACTORY_HOME/access OR $ARTIFACTORY_HOME/etc/security/access dirs exist at the time of the startup
      2.The $ARTIFACTORY_HOME/etc/db.properties file exists at the time of the startup
      3.The $ARTIFACTORY_HOME/etc/ha-node.properties file was missing during the first startup, which means Artifactory will not boot in HA mode, leading to it ignoring the bootstrap bundle.

      This leads to an inconsistent state where Artifactory will generate the access dirs from scratch, creating the private key/fingerprint mismatch scenario.

      This situation should not happen. If the bootstrap.bundle.tar.gz is placed in the $ARTIFACTORY_HOME/etc dir deliberately, it should not be considered legitimate to create new access dirs and communication.key which is mismatching the one in bootstrap bundle. It's better to fail startup with an informative error, so the Artifactory administator will be able to correct whatever caused the bootstrap bundle to be ignored.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                uriahl Uriah Levy
              • Votes:
                3 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: