MAAS 2.0 and "auto-assign" addresses

Bug #1578809 reported by Rod Smith on 2016-05-05
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

MAAS 2.0 eliminates the differentiation between "temporary" and "static" DHCP addresses that was present in MAAS 1.9, so when running for MAAS 2.0, maniacs-setup merges the two ranges into one. This is all well and good, except that MAAS now has a separate "auto-assign" range (and has since 1.9). Under 2.0, I suspect that MAAS is scanning the local network and assigning anything that's NOT detected as in-use. Unfortunately, it gets it wrong sometimes -- I just had it assign the address that my laptop uses to a node. (Grumble, grumble.) If I'm right, it could also "auto-assign" an address that's in use by a system that happens to be powered off. Offhand, I don't know how to tell MAAS to use some other range for these "auto" addresses, but this should be investigated and, if possible, controlled.

Rod Smith (rodsmith) on 2016-09-08
tags: added: server-cert
David Hayes (evidex) wrote :

I'm facing this at the minute as well. I get around it by deploying a DHCP server on the network and letting MAAS get an address within a range from that. Would love if it was possible to specify the ranges to be considered when 'auto-assigning' an address.

Rod Smith (rodsmith) wrote :


Are you using the Canonical certification suite, or is your problem with MAAS generally? If your problem is with MAAS generally, you may want to file a separate bug, since this one is against the specialized maas-cert-server package -- the intent of this bug is to find a workaround to MAAS's new model of assigning IP addresses, not to change this new MAAS operation.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers