Request for Latest Compatible Pulp 3 Versions and Upgrade Procedure for RHEL 9.5

#1

We have installed Pulp 3 on RHEL 9.5 hosts using the procedure outlined below. We now seek to upgrade to the latest compatible version. Could you please provide the latest compatible versions of the following Pulp services for RHEL 9.5 and share the procedure to upgrade to these versions while ensuring no impact on existing repositories?

Procedure we used to install pulp3: Getting started - Pulp Installer

pip list |grep -i pulp

pulp-cli 0.21.4
pulp-container 2.14.8
pulp-file 1.12.0
pulp-glue 0.21.4
pulp-rpm 3.19.11
pulpcore 3.22.34

==> This is our install.yml file used to install pulp3

cat install.yml

  • hosts: localhost
    force_handlers: True
    collections:
    • pulp.pulp_installer
      vars:
      pulp_settings:
      secret_key: “XXXXXXXXXXXXXXXXXXX”
      content_origin: “https://produs3-c1-yumrepo-s2-z1-0”
      pulp_default_admin_password: “XXXXXXXX”
      ansible_python_interpreter: /usr/bin/python3
      pulp_install_plugins:

      galaxy-ng:

      pulp-2to3-migration:

      pulp-ansible:

      pulp-certguard:

      pulp-container:
      version: “2.14.8”
      pulp-cli:
      version: “0.21.4”

      pulp-cookbook:

      pulp-deb:

      pulp-file:

      pulp-gem:

      pulp-glue:
      version: “0.21.4”

      pulp-maven:

      pulp-npm:

      pulp-python:

      pulp-rpm:
      version: “3.19.11”
      roles:
    • pulp_all_services
      environment:
      DJANGO_SETTINGS_MODULE: pulpcore.app.settings

      [py3_hosts:vars]

#2

The pulp-installer has been discontinued for over 2 years now, we now use containers to deploy Pulp. We have a migration guide that we wrote (Migrate from pulp_installer to a multi-process container - Pulp Project), but we haven’t tested it in a long time. Make sure you backup your postgres and artifacts before upgrading in case sometime goes wrong. We are now on version pulpcore 3.78 so it might make more sense to break up the upgrade into multiple jumps, one for each breaking change release.

So here are the steps I would follow:

  1. Make backups of postgres and artifacts.
  2. Follow the guide to switch over to running a Pulp container at the same pulpcore version 3.22 (for the final podman/docker run step add the version tag to the image, e.g. pulp/pulp:3.22)
  3. After checking everything still works, shut down the container and then re-run the container with the next pulpcore upgrade version. The new container should handle the upgrade and database migrations. It’s probably best to make backups between each upgrade in case of a problem.
  4. The pulpcore version order I would follow would be: 3.22 → 3.24 → 3.25 → 3.39 → 3.40 → 3.54 → 3.55 → 3.69 → 3.70 → 3.78. The versions in bold are breaking change releases, so when upgrading to their preceding version check the logs for any messages about management commands that need to be ran before upgrading to the breaking release.
2 Likes