OK so there's some issues in the prepare-silo job that are causing silos to be assigned but the assignment not reflected in bileto.
I have a fix for this but it's untested so you'll have to wait until next week for me to get back and finish it off. If this happens to you in the meantime, you need to review the log from the prepare silo job from the first time you ran it (you probably ran it a couple times and on subsequent runs saw the message "already assigned", so go back to the first time you ran it, there'll be a traceback but just before the traceback it'll say " configuring for silo ubuntu/landing-xxx" Just copy & paste the silo name from that log to the siloname field in bileto and then everything will work after that. Sorry for the inconvenience!
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
