buildbot
Old build master still exists
In the Builds-Build Masters Tab, the old master I used months ago still exists and the workers are connected to it.
I also notice this issue. I notice it when I have a dev instance and I rename the hostname (and buildbotURL and similar entries in master.cfg), and bring up new buildbot instance.
I think that's because the "masters" table in database has the entry for previous build master.
@tardyp Can we safely delete that old master entry from "masters" table in database? or is there any other/better way to delete old masters?
The master table is here to be able to support multimaster. If you change hostname or change path of master, then, this will create another master.
Problem with erasing a master is that you will need to cascade delete all the data that is associated with it (or the db engine will complain about foreign key issue). Notably, all builds record which master they built on.
This is something we could do in the Janitor step. If after some times there is no build associated with a master anymore, its time to delete it from the db.
most of my workers connect to the new master, but two of them connect to both the old and the new one. Is there any way to stop this from happening?
Also seeing workers connected to an old master that no longer exists. Is there a way to stop the worker from connecting to the non-existent master? Not sure if the potential Janitor step has been implemented or if there is a way to do this manually.
Hey, is there any progress on this topic. I got similar issue. When I stop my workers they are all in green state although I've stopped them. When I start them again, the correct master is showing and slaves are connected successfully. Every build works fine, that's not the problem, its just the always active state that is not changing when I stop the slaves. Can anyone tell if the problem is the old masters that are still showing or the issues is different?
