Similarly, for MAAS 1.9 users who have migrated from a MAAS 1.8 database containing leaked IP addresses, running "sudo maas-region-admin dbshell" and then executing the SQL found here[1] fixes it:
delete from maasserver_staticipaddress ip
where ip.id in (
select ip.id from maasserver_staticipaddress ip
left outer join maasserver_interface_ip_addresses iip
on ip.id = iip.staticipaddress_id where iip.id is null and ip.alloc_type=1
);
For MAAS 1.8 users, we have a workaround: delete any static IP addresses not associated with a MAC address. A script to do so is available here:
http:// pastebin. ubuntu. com/14423324/
Similarly, for MAAS 1.9 users who have migrated from a MAAS 1.8 database containing leaked IP addresses, running "sudo maas-region-admin dbshell" and then executing the SQL found here[1] fixes it:
delete from maasserver_ staticipaddress ip staticipaddress ip interface_ ip_addresses iip ress_id
where iip.id is null and ip.alloc_type=1
where ip.id in (
select ip.id from maasserver_
left outer join maasserver_
on ip.id = iip.staticipadd
);
[1]: https:/ /bugs.launchpad .net/maas/ +bug/1519527/ comments/ 46