Upgrading Anaconda Server


Caution

Before you upgrade, create backups of the docker-compose.yml and .env files. These files contain your server’s custom configurations and are overwritten during the upgrade.

Service account roles

If you are currently using Anaconda Server 6.1.6 or later, you may skip these steps and start upgrading.

Before you upgrade, you must verify that the correct permissions are set for the service account. If you do not, the Keycloak API will not be able to query user roles and users will lose all their assigned permissions.

  1. Open a browser and log into your Keycloak admin panel using your existing Keycloak credentials. Your Keycloak admin panel can be found at www.<YOUR_DOMAIN>/auth/admin.
  2. Navigate to the Clients page from the left-hand navigation menu, then select repo-account-sync from the list.
  3. Select the Service Account Roles tab at the top of the page, then open the Client Roles dropdown menu and select realm-management.
  4. Add manage-users and manage-realm to the Assigned Roles.

Upgrading to a newer version

Anaconda Server versions 6.1.4 and later support upgrading from your current version without halting the program.

Upgrade steps

  1. Download your installer by running the command:

    # Replace <INSTALLER_LOCATION> with the provided installer location
curl -O <INSTALLER_LOCATION>

  2. Run the upgrade command.

    HTTP setup upgrade command

    To upgrade Anaconda Server using the default upgrade command, run:

    # Replace <INSTALLER> with the installer you just downloaded
# Replace <PATH_TO_REPO_FOLDER> with the path to your repository - the default path is /opt/anaconda/repo
# Replace <FQDN> with your fully qualified domain name
# Replace <PREVIOUS_INSTALLER> with the location of the previous installer file (where the docker-compose.yml is located)
bash <INSTALLER>  -- -b <PATH_TO_REPO_FOLDER> -d <FQDN> --upgrade-from ../<PREVIOUS_INSTALLER>

    For example, if your domain name is website.example.com, and the previous installer is located at /home/user/installers/ate-installer-6.1.6-7d5m23wl, then the upgrade command would be the following:

    bash as-installer-6.2.0-0fj4r5a1.sh -- -b /opt/anaconda/repo -d website.example.com --upgrade-from ../ate-installer-6.1.6-7d5m23wl

  3. Once the upgrade is complete, run the following command to instruct Keycloak to allow HTTP traffic:

    # Replace <ADMIN_PASSWORD> with the password used to log in to Keycloak as user "admin"
docker-compose exec -T keycloak ./bin/kcadm.sh update realms/master -s sslRequired=NONE --server [http://localhost:8080/auth> --realm master --user admin --password <ADMIN_PASSWORD>

    HTTPS setup upgrade command

    The default command will upgrade your software, but your setup may require you to append more arguments to the command in order to complete an upgrade. For example, if your setup uses HTTPS protocol, you’ll need to provide the TLS certificate and key in your installation command:

    # Replace <INSTALLER> with the installer you just downloaded
# Replace <PATH_TO_REPO_FOLDER> with the path to your repository - the default path is /opt/anaconda/repo
# Replace <FQDN> with your fully qualified domain name
# Replace <PATH_TO_CERT> and <PATH_TO_KEY> with your TLS certificate and key paths
# Replace <PREVIOUS_DIR> with the location of the previous installation (where the docker-compose.yml is located)
bash <INSTALLER> -- -b <PATH_TO_REPO_FOLDER> --domain <FQDN> --tls-cert <PATH_TO_CERT> --tls-key <PATH_TO_KEY> --upgrade-from ../<PREVIOUS_INSTALLER>

    You can see a full list of command arguments by running the following commands:

    # Replace <INSTALLER> with the installer you just downloaded
cd <INSTALLER>
bash ./install.sh --help

    Custom implementation considerations

    If you’re using a custom implementation, verify your docker-compose.yml and/or repo.conf (nginx configuration) files reflect the upgraded changes.