Comment 5 for bug 578338

Given the comments from bigjools danilo and noodles, LPCONFIG looks like the key. Chex let me look at the script that starts the buildd-manager: https://pastebin.canonical.com/32161/ . I think it is very suspicious that the script does not export LPCONFIG in start_buildd_manager, as it does for stop_buildd_manager? As danilo pointed out on IRC, this might explain the observed behavior: first it doesn't work, then you stop (and LPCONFIG is exported!) and then you start and it does work.

Could LOSAs add the export in start_buildd_manager and see if it addresses the problem?

Thank you