Build creation is restricted only to the PocketChroot presence, not the chroot itself

Bug #384054 reported by Celso Providelo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Celso Providelo

Bug Description

SPPH.createMissingBuilds() calculates distroarchseries availability by simply checking the presence of a corresponding PocketChroot record.

This is incompatible with the way chroots are handled, when they are deleted, the PocketChroot remains and only it's 'chroot' attribute it cleared.

IFW, createMissingBuilds() should use DAS.getChroot() instead of DAS.getPocketChroot().

This problem exposes a possible underlying issue with buildd-manager when it tries to dispatch a job for which it cannot find the chroot. It simply blocks, waiting an extra interaction with the targeted builder.

Celso Providelo (cprov)
summary: - Build creation is restricted only to PocketChroot present, not the
+ Build creation is restricted only to the PocketChroot presence, not the
chroot itself
Celso Providelo (cprov)
Changed in soyuz:
status: Triaged → In Progress
Revision history for this message
Celso Providelo (cprov) wrote :

r8543 (devel)

Changed in soyuz:
status: In Progress → Fix Committed
Celso Providelo (cprov)
Changed in soyuz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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