[users at bb.net] New masters being created after restart

[Mojca Miklavec]

On Wed, 19 Aug 2020 at 18:27, Povilas Kanapickas wrote:
> On 8/19/20 11:27 AM, Lukas Jirkovsky wrote:
> > Hello,
> > I have a problem with new masters being created after every restart.
> >
> > We are running buildbot-master using docker image
> > buildbot/buildbot-master:v2.7.0. The database is postgres 12.2 also
> > running in docker. Whenever the container is restarted, a new build
> > master is created. This has happened quite a few times recently for
> > technical reasons when the server hosting buildbot had to be
> > restarted.
> >
> > The list of build masters now shows a lot of masters with all except
> > one being inactive. I think this has also caused an issue where two of
> > the builders no longer work despite their workers are online, because
> > I can see that the workers are now listed with two build masters which
> > has never happened before.
>
> IIRC the name of the master is set according to the hostname of the
> docker instance. And docker instance will have a random hostname each time.
>
> This could be solved by forcing a static hostname using the hostname
> attribute in docker-compose (or the equivalent in docker command line).

I was also bitten by this problem whenever I set up a buildbot master
on my laptop. Whenever I switch to a different WiFi when moving
around, I get a new buildbot master created, and sometimes the status
even gets stuck (I forgot all the details). It's pretty annoying.
There could at least be an option inside the buildbot master saying
that "this setup only has one buildbot master, please don't bother
creating dozens of additional defunct ones".

It was just for testing anyway, so it wasn't so extremely bad, it was
just annoying.

Mojca