Project

Profile

Help

Issue #2253

pulp status call hangs if qpid is unresponsive

Added by cduryee over 5 years ago. Updated almost 3 years ago.

Status:
CLOSED - NOTABUG
Priority:
High
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Sprint 9
Quarter:

Description

If you suspend the qpid process, calls to the pulp API status call will not return. Unsuspending the process will make the calls complete.

For example:

kill -19 `pidof qpidd`
curl -k -u admin:admin https://localhost/pulp/api/v2/status/

in another window:
kill -18 `pidof qpidd`

the status call will then return. This can become an issue if qpid is heavily loaded, it may be better for Pulp to just return that it wasn't able to connect after X amount of time.

History

#1 Updated by amacdona@redhat.com over 5 years ago

  • Priority changed from Normal to High
  • Severity changed from 2. Medium to 3. High
  • Triaged changed from No to Yes

#2 Updated by mhrivnak over 5 years ago

  • Sprint/Milestone set to 27

#3 Updated by pcreech over 5 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to pcreech

#4 Updated by pcreech over 5 years ago

  • Status changed from ASSIGNED to CLOSED - NOTABUG

This has been isolated to an issue with older versions of python-qpid where the connect action won't timeout. Newer versions do not have this issue anymore.

Tested on latest python-qpid in fedora with success

#5 Updated by bmbouter almost 4 years ago

  • Sprint set to Sprint 9

#6 Updated by bmbouter almost 4 years ago

  • Sprint/Milestone deleted (27)

#7 Updated by bmbouter almost 3 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF