downstream foreman maintain starts the pulp services prior to migration. It seems that the pulp3 services aren't always up: {:services=> {:candlepin=>{:status=>"ok", :duration_ms=>"26"}, :candlepin_auth=>{:status=>"ok", :duration_ms=>"36"}, :foreman_tasks=>{:status=>"ok", :duration_ms=>"3"}, :katello_events=> {:status=>"ok", :message=>"0 Processed, 0 Failed", :duration_ms=>"0"}, :candlepin_events=> {:status=>"ok", :message=>"0 Processed, 0 Failed", :duration_ms=>"0"}, :pulp3=>{:status=>"FAIL", :message=>"503 Service Unavailable"}, :pulp=>{:status=>"ok", :duration_ms=>"98"}, :pulp_auth=>{:status=>"ok", :duration_ms=>"57"}}, :status=>"FAIL"} (the katello/candlepin events messages just need something to hit the webserver). We need some sort of sleep for 30 seconds if the pulp3 server is throwing a 503.
Created from redmine issue https://projects.theforeman.org/issues/31644
Upstream bug assigned to None
may be fixed by https://bugzilla.redhat.com/show_bug.cgi?id=1918464
We believe this has been resolved by a bug in the pulpcore service definitions that were incorrectly setting the systemd type.
Verified python3-pulpcore-3.7.3-1.el7pc.noarch Checked on an upgraded instance. 6.8 -> 6.9. $ grep -n Type= `find /etc/systemd/system -name pulpcore-*.service` /etc/systemd/system/pulpcore-api.service:7:Type=notify /etc/systemd/system/pulpcore-content.service:7:Type=notify /etc/systemd/system/pulpcore-resource-manager.service:7:Type=simple /etc/systemd/system/pulpcore-worker@.service:7:Type=simple $ satellite-maintain service status . . . - All services are running [OK]
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Satellite 6.9 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:1313