It is absolutely a bug in MAAS if it offers up addresses to be used that
it knows are already used.
I have to believe it would be easier to fix this bug in MAAS than to
work around it in Landscape. Only MAAS knows all the different ways an
IP address might be used:
* attached to an Interface on a Node
* attached to a MACAddress on a Device
* associated with a BMC or other controller
* allocated to a range for some other purpose
There is, or should be, a single function call in MAAS which determines
ranges available. That single function call needs to be fixed to know
about all thee ways an address can be allocated or consumed.
So, to my mind, working around this in Landscape is exactly wrong; it
doubles the total amount of work needed to be done by Canonical to get a
good result (we do it in Landscape and AGAIN in MAAS) and leaves MAAS
buggy in an obvious and important way.
Please reconsider. If needed, have someone on the Landscape team submit
the fix to MAAS.
Can we agree that this is at best a workaround?
It is absolutely a bug in MAAS if it offers up addresses to be used that
it knows are already used.
I have to believe it would be easier to fix this bug in MAAS than to
work around it in Landscape. Only MAAS knows all the different ways an
IP address might be used:
* attached to an Interface on a Node
* attached to a MACAddress on a Device
* associated with a BMC or other controller
* allocated to a range for some other purpose
There is, or should be, a single function call in MAAS which determines
ranges available. That single function call needs to be fixed to know
about all thee ways an address can be allocated or consumed.
So, to my mind, working around this in Landscape is exactly wrong; it
doubles the total amount of work needed to be done by Canonical to get a
good result (we do it in Landscape and AGAIN in MAAS) and leaves MAAS
buggy in an obvious and important way.
Please reconsider. If needed, have someone on the Landscape team submit
the fix to MAAS.
Mark