Bug #31644
closedcontent migration may fail if pulp isn't up yet
Description
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.