November 18

Linux: Satellite upgrade notes

Installation:Document used:
In general the Red Hat directions work the biggest caveat came when running the health check: [root@ServerName ~]# foreman-maintain upgrade check –target-version 6.3
It kept failing on Satellite due to running tasks background.
foreman-maintain upgrade check –target-version 6.3 Running Checks before upgrading to Satellite 6.3Example output:

Check for paused tasks: [OK] Check whether all services are running using hammer ping: [OK] Check to validate candlepin database: [OK] Check for running tasks: [FAIL] There are 11 active task(s) in the system. Please wait for these to complete or cancel them from the Monitor tab.There are multiple steps to proceed:1) Fetch tasks status and wait till they finish2) Investigate the tasks via UISelect step to continue, [n(next), q(quit)]

The fix was to get into Postgres and disable the jobs manually.
This will list running jobs from postgres:su – postgres -c “psql -d foreman -c ‘select label,count(label),state from foreman_tasks_tasks where state <> ‘\”stopped’\” group by label,state;'”

Example output:
Actions::RemoteExecution::RunHostsJob | 79 | scheduledActions::RemoteExecution::RunHostJob | 11 | runningActions::Katello::EventQueue::Monitor | 1 | runningActions::Insights::EmailPoller | 1 | scheduledActions::Candlepin::ListenOnCandlepinEvents | 1 | running(5 rows)

Notice RunHostsJob is listed as scheduled and RunHostJob is listed as running.  Both of these will cause the health check to fail.
To stop these do run the following command:foreman-rake foreman_tasks:cleanup TASK_SEARCH=’label = Actions::RemoteExecution::RunHostsJob’ STATES=’running,pending,planned,paused,scheduled,planning’ VERBOSE=trueforeman-rake foreman_tasks:cleanup TASK_SEARCH=’label = Actions::RemoteExecution::RunHostJob’ STATES=’running,pending,planned,paused,scheduled,planning’ VERBOSE=true
Now the health check will work.

After pushing out the agent
There is some clean up that needs to take place for yum to work properly on the Red Hat servers connected to Satellite.1. Go to Content View2. Select a view3. Select the Yum Content tab 4. Click Repositories5. Remove the old Satellite Repository by selecting the old one and clicking Remove Repositories6. Click add, find the new Satellite repository and click Add Repositories7. Click the Versions tab8. Go through the process of Publishing a new version and Promoting each Environment.
Once this is complete the client servers will see the new Satellite repository files and work properly.

Copyright 2021. All rights reserved.

Posted November 18, 2021 by Timothy Conrad in category "Linux

About the Author

If I were to describe myself with one word it would be, creative. I am interested in almost everything which keeps me rather busy. Here you will find some of my technical musings. Securely email me using - PGP: 4CB8 91EB 0C0A A530 3BE9 6D76 B076 96F1 6135 0A1B