Project

Profile

Help

Issue #478

closed

Pulp sync'ing should gracefully handle inability to resolve hostname

Added by jsherril@redhat.com about 9 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Low
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
1. Low
Version:
2.4 Beta
Platform Release:
2.6.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

++ This bug was initially created as a clone of Bug #1124616 ++

During a sync from a remote repository such as the CDN, if the hostname of the source is unable to be resolved, the sync task can become indefinitely stuck and unrecoverable. The scenario by which I encountered this:

For Sync'ing:
Import a manifest
Enable Jboss repository
Start sync of Jboss repository
Pull network cable from box (effectively removing ability to reach DNS servers)
Sync progress part sat as if progress was being made but never changed

I then replaced the network cable and ran a 'katello-service restart' at which point the last node hung at being stopped (same issue you saw). I terminated the service restart, killed the pulp workers with 'kill -9' and then was able to cleanly run 'katello-service' restart. At which point, I was able to re-run a sync successfully. Note for Pulp's sake, the 'katello-service restart' restarts all Pulp services including workers, resource managers and celery beat.

--- Additional comment from RHEL Product and Program Management on 2014-07-29 19:13:32 EDT ---

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

--- Additional comment from RHEL Product and Program Management on 2014-07-29 19:14:57 EDT ---

Since this issue was entered in Red Hat Bugzilla, the pm_ack has been
set to + automatically for the next planned release

+ This bug was cloned from Bugzilla Bug #1124625 +

Also available in: Atom PDF