Silo configured "half way" after an error about lack of test plan

Bug #1494628 reported by Timo Jyrinki
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
CI Train [cu2d]
Fix Released
Undecided
Robert Bruce Park

Bug Description

After this errored out prepare-silo:
https://ci-train.ubuntu.com/job/prepare-silo/6123/console "ERROR Field "test_plan" is mandatory."

Bileto started thinking the request:
https://ci-train.ubuntu.com/job/prepare-silo/6126/console "ERROR Request 332 already assigned." was already assigned.

Even though it does not actually look like so if looking at the request https://requests.ci-train.ubuntu.com/#/ticket/332.

But then, 014 silo does seem to be assigned according to running another prepare-silo for a new identical request: https://ci-train.ubuntu.com/job/prepare-silo/6127/console

So it seems it both is and isn't assigned.

Related branches

description: updated
description: updated
Revision history for this message
Robert Bruce Park (robru) wrote :

Well, I couldn't sleep and decided to work on this, found a simple solution ;-)

My branch should prevent this situation from happening again, however to fix your existing request in an inconsistent state, you'll need to manually set the siloname field in bileto to ubuntu/landing-NNN and then it should work just fine, from there you can either free it (since you already have the identical other one) or use it.

affects: bileto → cupstream2distro
Changed in cupstream2distro:
status: New → In Progress
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Thanks! Freed up the silo/request now.

Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:cupstream2distro at revision 1095, scheduled for release in cupstream2distro, milestone Unknown

Changed in cupstream2distro:
status: In Progress → Fix Committed
Changed in cupstream2distro:
status: Fix Committed → Fix Released
assignee: nobody → Robert Bruce Park (robru)
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.