Troubleshooting BlueCat Server Update Service upgrades - Adaptive Applications - BlueCat Gateway - 26.1.1

BlueCat Server Update Services Administration Guide
ft:locale
en-US
Product name
BlueCat Gateway
Version
26.1.1

Starting in BSUS 25.2.2, the application runs the Portal container as a non-root user, with the UID and GID 9000, and validates write access to all mounted paths at start up.

During an upgrade, existing Docker volumes may be owned by the root user or another UID, causing the Portal container to enter a restart loop with errors similar to the following:
  • No access to folder 'logs'
  • No access to folder 'bluecat_gateway'

To resolve this issue, use one of the following methods:

Upgrading to BSUS v25.2.2 or greater from versions earlier than 25.2

  1. Stop the BSUS container using the following command:
    docker-compose down
  2. Update the ownership and permissions of the directory to the non-root user using the following command:
    sudo chown -R 9000:9000 /var/lib/docker/volumes/bsus_portal_logs/_data
  3. Start the BSUS container using the following command:
    docker-compose up -d

Upgrading to BSUS v25.2.2 or greater from versions 25.2 and 25.2.1

  1. Stop the BSUS container using the following command:
    docker-compose down
  2. Update the ownership and permissions of the directory to the non-root user using the following command:
    sudo chown -R 9000:9000 /var/lib/docker/volumes/bsus_portal_logs/_data
  3. Update the volume mapping in the docker-compose.yml file with the following changes:
    • When upgrading to BSUS v26.1: Keep the mapping as bluecat_portal:/portal/bluecat_portal/
    • When upgrading to BSUS v25.2.2: Update the mapping from bluecat_portal:/portal/bluecat_portal/ to bluecat_portal:/bluecat_gateway
    • For the bluecat_portal volume, do not set the value external: true, as a new volume must be created for the upgrade.
  4. Remove existing volumes that cause issues using the following commands:
    docker volume ls | grep -E '(bsus|dist)_bluecat_portal'
docker volume rm <bsus_bluecat_portal or dist_bluecat_portal>
    Important: This volume stores Gateway configurations created through the UI including uploaded certificates, Address Manager settings, interface preferences, logging configurations, and additional customizations.

    Updating or recreating this volume removes all Gateway configuration data stored in it. If you uploaded any certificates through the UI, you must re-upload them after the change. For more information, refer to Configuring Certificates settings.

  5. Start the BSUS container using the following command:
    docker-compose up -d