Ok, I've managed to reproduce this locally with by having to rack controllers, one that can access the BMC via layer2, and the other that has layer3 access only.
If I turn off the first rack controller, I get the same error. There's code that should try all rack controllers if it can't find any that has a direct connection, but for some reason that code doesn't work. Will have to look into that.
To work around it, I manually inserted a row in the maasserver_bmcroutablerackcontrollerrelationship:
Ok, I've managed to reproduce this locally with by having to rack controllers, one that can access the BMC via layer2, and the other that has layer3 access only.
If I turn off the first rack controller, I get the same error. There's code that should try all rack controllers if it can't find any that has a direct connection, but for some reason that code doesn't work. Will have to look into that.
To work around it, I manually inserted a row in the maasserver_ bmcroutablerack controllerrelat ionship:
https:/ /paste. ubuntu. com/p/TFR6VT8sz h/
That's the table that MAAS should update if it doesn't find a rack controller that can currently connect to the BMC.