Project

General

Profile

Actions

Bug #31644

closed

content migration may fail if pulp isn't up yet

Added by Justin Sherrill over 3 years ago. Updated over 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Tooling
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

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.

Actions

Also available in: Atom PDF