Bug 726709 - pulp locks up at random points during automation
Summary: pulp locks up at random points during automation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Pulp
Classification: Retired
Component: user-experience
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Jason Connor
QA Contact: dgao
URL:
Whiteboard:
Depends On:
Blocks: verified-to-close
TreeView+ depends on / blocked
 
Reported: 2011-07-29 15:06 UTC by dgao
Modified: 2014-03-31 01:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-16 12:07:53 UTC
Embargoed:

Attachments (Terms of Use)

Description dgao 2011-07-29 15:06:49 UTC 
Automation run on both qe and nightly build 0.0.217 seems to lock up pulp at random points.

For qe build, pulp-admin repo status --id=parent_clone_repo

For nightly build, pulp-admin package install -n origin --consumerid=test_consumer

In both cases, the following traceback is observed:


2011-07-29 10:58:00,915 21698:140730572990208: pulp:CRITICAL: queue:128 Exception in FIFO Queue Dispatch Thread
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/pulp/server/tasking/taskqueue/queue.py", line 124, in _dispatch
    self._timeout_tasks()
  File "/usr/lib/python2.7/site-packages/pulp/server/tasking/taskqueue/queue.py", line 185, in _timeout_tasks
    task.timeout()
TypeError: 'datetime.timedelta' object is not callable
Comment 1 Jason Connor 2011-07-29 15:21:08 UTC 
fix pushed in a0f6bfd66863ac5dcfee40544a987c2a657bdc3f
Turned out to be a name conflict between a field and a method of Task
Comment 2 Jay Dobies 2011-07-29 20:44:05 UTC 
Fixed in 0.218
Comment 3 dgao 2011-08-02 14:40:31 UTC 
The issue no longer exists in automation, closing.
Comment 4 Preethi Thomas 2011-08-16 12:07:53 UTC 
Closing with Community Release 15

pulp-0.0.223-4.
Comment 5 Preethi Thomas 2011-08-16 12:21:16 UTC 
Closing with Community Release 15

pulp-0.0.223-4.
Note You need to log in before you can comment on or make changes to this bug.