[root@dhcp-3-234 server]# satellite-maintain prep-6.10-upgrade
Running Preparations for the Satellite 6.10 upgrade
================================================================================
Preparations for the Satellite 6.10 upgrade:
prep-6.10-upgrade may take a while depending on the size of /var/lib/pulp/content
| $ chown -R :pulp /var/lib/pulp/content [OK]
--------------------------------------------------------------------------------
[root@dhcp-3-234 server]# satellite-maintain content prepare
Running Prepare content for Pulp 3
================================================================================
Start applicable services:
Starting the following service(s):
rh-mongodb34-mongod, postgresql, qdrouterd, qpidd, rh-redis5-redis, squid, pulp_celerybeat, pulp_resource_manager, pulp_streamer, pulp_workers, smart_proxy_dynflow_core, tomcat, dynflow-sidekiq@orchestrator, foreman, httpd, puppetserver, dynflow-sidekiq@worker, dynflow-sidekiq@worker-hosts-queue, foreman-proxy
/ All services started [OK]
--------------------------------------------------------------------------------
Enable applicable services:
Enabling the following service(s):
pulpcore-api, pulpcore-content, pulpcore-resource-manager, pulpcore-worker@1, pulpcore-worker@2, pulpcore-worker@3, pulpcore-worker@4
/ enabling pulpcore-resource-manager
Created symlink from /etc/systemd/system/multi-user.target.wants/pulpcore-api.service to /etc/systemd/system/pulpcore-api.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/pulpcore-content.service to /etc/systemd/system/pulpcore-content.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/pulpcore-resource-manager.service to /etc/systemd/system/pulpcore-resource-manager.service.
| enabling pulpcore-worker@4
Created symlink from /etc/systemd/system/multi-user.target.wants/[email protected] to /etc/systemd/system/[email protected].
Created symlink from /etc/systemd/system/multi-user.target.wants/[email protected] to /etc/systemd/system/[email protected].
Created symlink from /etc/systemd/system/multi-user.target.wants/[email protected] to /etc/systemd/system/[email protected].
Created symlink from /etc/systemd/system/multi-user.target.wants/[email protected] to /etc/systemd/system/[email protected].
/ All services enabled [OK]
--------------------------------------------------------------------------------
Start applicable services:
Starting the following service(s):
pulpcore-api, pulpcore-content, pulpcore-resource-manager, pulpcore-worker@1, pulpcore-worker@2, pulpcore-worker@3, pulpcore-worker@4
/ All services started [OK]
--------------------------------------------------------------------------------
Prepare content for Pulp 3:
Checking for valid Katello configuraton.
rake aborted!
The following services have not been started or are reporting errors: candlepin, foreman_tasks, pulp3
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.18.1.40/app/models/katello/ping.rb:35:in `ping!'
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.18.1.40/lib/katello/tasks/pulp3_migration.rake:13:in `block (2 levels) in <top (required)>'
/opt/rh/rh-ruby25/root/usr/share/gems/gems/rake-12.3.3/exe/rake:27:in `<top (required)>'
Tasks: TOP => katello:pulp3_migration
(See full trace by running task with --trace)
[FAIL]
Failed executing foreman-rake katello:pulp3_migration, exit status 1
--------------------------------------------------------------------------------
Scenario [Prepare content for Pulp 3] failed.
The following steps ended up in failing state:
[content-prepare]
Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="content-prepare"
root@dhcp-3-234 server]# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● cloud-final.service loaded failed failed Execute cloud user/final scripts
● pulp_celerybeat.service loaded failed failed Pulp's Celerybeat
● rh-mongodb34-mongod.service loaded failed failed High-performance, schema-free document-oriented dat
● [email protected] loaded failed failed Migrate local SELinux policy changes from the old
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
4 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
root@dhcp-3-234 server]# systemctl | grep -E 'pulp|candlepin|foreman'
foreman-proxy.service loaded active running Foreman Proxy
foreman.service loaded active running Foreman
● pulp_celerybeat.service loaded failed failed Pulp's Celerybeat
pulp_resource_manager.service loaded active running Pulp Resource Manager
pulp_streamer.service loaded active running The Pulp lazy content loading streamer
pulp_worker-0.service loaded active running Pulp Worker #0
pulp_worker-1.service loaded active running Pulp Worker #1
pulp_worker-2.service loaded active running Pulp Worker #2
pulp_worker-3.service loaded active running Pulp Worker #3
pulp_worker-4.service loaded active running Pulp Worker #4
pulp_worker-5.service loaded active running Pulp Worker #5
pulp_workers.service loaded active exited Pulp Celery Workers
pulpcore-api.service loaded active running Pulp API Server
pulpcore-content.service loaded active running Pulp Content App
pulpcore-resource-manager.service loaded active running Pulp Resource Manager
[email protected] loaded active running Pulp RQ Worker
[email protected] loaded active running Pulp RQ Worker
[email protected] loaded active running Pulp RQ Worker
[email protected] loaded active running Pulp RQ Worker
system-pulpcore\x2dworker.slice loaded active active system-pulpcore\x2dworker.slice
foreman.socket loaded active running Foreman HTTP Server Accept Sockets
pulpcore-api.socket loaded active running Pulp API Server socket
pulpcore-content.socket loaded active running Pulp Content App socket
Comments