Red Hat Capsule is not connecting to Satellite server after upgrade from 6.14 to 6.15

Solution Verified - Updated

Environment

  • Red Hat Capsule 6.15

Issue

  • After upgrade from the 6.14 to the 6.15 release, Capsule server is not connecting to Satellite server.

Resolution

  • Execute the following command on the Capsule server to run the skipped databse migrations:

    # PULP_SETTINGS='/etc/pulp/settings.py' DJANGO_SETTINGS_MODULE='pulpcore.app.settings' pulpcore-manager migrate --noinput

Reach out to the This content is not included.Red Hat Technical Support in case any further assistance would be required.

For more KB articles/solutions related to Red Hat Satellite 6.x Installation/Upgrade/Update Issues, please refer to the Red Hat Satellite Consolidated Troubleshooting Article for Red Hat Satellite 6.x Installation/Upgrade/Update Issues.

Root Cause

The following database migration was not performed during the upgrade:

Applying core.0099_versions_field... OK

This happened because the following packages were manually updated via yum update before the satellite-installer was run on the Capsule, which broke the upgrade.

Diagnostic Steps

  • A django.db.utils.ProgrammingError: column core_worker.versions does not exist is logged in /var/log/messages on the Capsule server:

    .
.
May 29 01:50:17 capsule pulpcore-worker-7[675453]:    return self.cursor.execute(sql, params)
May 29 01:50:17 capsule pulpcore-worker-7[675453]:           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
May 29 01:50:17 capsule pulpcore-worker-7[675453]:  File "/usr/lib/python3.11/site-packages/psycopg/cursor.py", line 723, in execute
May 29 01:50:17 capsule pulpcore-worker-7[675453]:    raise ex.with_traceback(None)
May 29 01:50:17 capsule pulpcore-worker-7[675453]: django.db.utils.ProgrammingError: column core_worker.versions does not exist
May 29 01:50:17 capsule pulpcore-worker-7[675453]: LINE 1: ...e_worker"."name", "core_worker"."last_heartbeat", "core_work...
May 29 01:50:17 capsule pulpcore-worker-7[675453]:                                                             ^
May 29 01:50:18 capsule systemd[1]: pulpcore-worker@8.service: Main process exited, code=exited, status=1/FAILURE
May 29 01:50:18 capsule systemd[1]: pulpcore-worker@8.service: Failed with result 'exit-code'.
May 29 01:50:18 capsule systemd[1]: pulpcore-worker@4.service: Main process exited, code=exited, status=1/FAILURE
May 29 01:50:18 capsule systemd[1]: pulpcore-worker@4.service: Failed with result 'exit-code'.
May 29 01:50:18 capsule systemd[1]: pulpcore-worker@5.service: Main process exited, code=exited, status=1/FAILURE
May 29 01:50:18 capsule systemd[1]: pulpcore-worker@5.service: Failed with result 'exit-code'.
May 29 01:50:18 capsule pulpcore-api[675503]: Error: This app must be executed using pulpcore-api entrypoint.
May 29 01:50:18 capsule systemd[1]: pulpcore-api.service: Main process exited, code=exited, status=1/FAILURE
May 29 01:50:18 capsule systemd[1]: pulpcore-api.service: Failed with result 'exit-code'.

  • In /var/log/foreman-installer/capsule.log on the Capsule server, no database migrations were performed during the upgrade:

    2024-12-02 12:00:55 [DEBUG ] [configure] Exec[pulpcore-manager migrate --noinput](provider=posix): Executing check 'pulpcore-manager migrate --plan | grep "No planned migration operations"'
2024-12-02 12:00:55 [DEBUG ] [configure] Executing with uid=pulp: 'pulpcore-manager migrate --plan | grep "No planned migration operations"'
2024-12-02 12:00:59 [DEBUG ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[migrate --noinput]/Exec[pulpcore-manager migrate --noinput]/unless:   No planned migration operations.
2024-12-02 12:00:59 [DEBUG ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[migrate --noinput]/Exec[pulpcore-manager migrate --noinput]: 'pulpcore-manager migrate --noinput' won't be executed because of failed check 'unless'
2024-12-02 12:00:59 [DEBUG ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[migrate --noinput]/Exec[pulpcore-manager migrate --noinput]: Evaluated in 3.53 seconds
SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.