Launchpad itself

build-manager loses track of buildds sometimes

Bug #541017 reported by LaMont Jones
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Medium
Unassigned

Bug Description

Sometimes, build-manager decides to ignore a buildd until at least tickled. Frequently, marking the buildd manual and then returning it to auto is sufficient to make buildd-manager see it again, other times nothing seems to make buildd-manager
notice the buildd again. In today's case, the last log entry for berkelium is:

2010-03-08 12:11:42+0000 [-] Builder 'berkelium' rescued from '1550051-3165289': 'No job assigned to builder'

And then nothing. -->manual-->auto did nothing, nor did marking it !OK, !active, and back.

recycled berkelium to see if that makes any difference, will follow up after that finishes.

lamont

Julian Edwards (julian-edwards)
Changed in soyuz:
status: New → Triaged
importance: Undecided → Medium
tags: added: buildd-manager
Revision history for this message
LaMont Jones (lamont) wrote :

recycling the ppa host worked around the issue.

lamont

Revision history for this message
Michael Nelson (michael.nelson) wrote :

This looks a lot like bug 463046?

Revision history for this message
William Grant (wgrant) wrote :

My initial response was the same as Michael's.

Revision history for this message
William Grant (wgrant) wrote :

LaMont: if this happens again, please run "import xmlrpclib; xmlrpclib.ServerProxy('http://somebuildd:8221/rpc').status()" in a Python interpreter and take note of the returned string. I suspect it will say "BuilderStatus.ABORTING", which would confirm that this is bug #463046.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.