I’ve been working through testing 2.8, and preparing internal documentation for our rollout of 2.8 and I hit a snag. It’s a bit of an odd one, and I’ve not seen this before, so any advice warmly welcomed.
I have a MAAS server with an internal network which is MAAS managed with DHCP setup as fabric-1 with an CIDR of 10.0.10.0/24. fabric-0 is on my local office lan and is used to WAN access and it’s where I generally access the system from. This is 10.0.0.0/24.
Fabric-0 is associated with an adapter which gets it’s address via DHCP, and I generally lock the IP for my MAAS setups as I don’t want to have to change the maas-url if the address changes, however I managed to forget to do this and had to use maas command line tool and change the address.
I generally just check over the subnets after I do this to make sure things look ok, and I find that 10.0.0.0 has moved to fabric-1.
But that’s ok, I’ll just move it back to the right fabric…
I guess my question, is this a bug ? It’s a tad annoying, but it can clearly be worked around.