More than one CI test fails with:
ERROR ('0/lxd/1', 'no obvious space for container "0/lxd/1", host machine has spaces: "ha-space", "space-0"')
This will occur randomly based on the node acquired on the finfolk machine.
At the time of writing there are 14 nodes (juju-qa-maas-node-31.maas through juju-qa-maas-node-41.maas). Of these, all have interfaces configured for the 10.0.30.0/24 subnet (space-0), but 3 also have a device in the 192.168.4.0/24 subnet (ha-space). These will be the ones blowing up tests if they happen to be acquired.
Now back in the day, Nicholas (balloons) informed our team that we could use these machines for testing. I myself created a new subnet and space. I suffixed the space name with “manadart” so it was obviously mine, and I have since deleted it.
I wonder if these issues are side-effects from someone’s space and subnet testing.
In any case, we have 2 obvious options:
- Write tests to be explicit about the space they bind to when provisioning.
- Make the finfolk networking homogeneous, with a single space.
I lean towards option 2, because option 1 couples the CI tests more tightly to the testing environment. Also because the additional spaces look like someone’s testing arrangement that has not been reverted.