To prevent the possibility of stale leases remaining in the StaticIPAddress table as DISCOVERED, an additional fix was needed to filter stale leases (in case an IP address was assigned to another host).
One issue remains that I found in testing: after the lease parser runs, the zone file isn't udpated. (Rather, I saw it get updated ~3 seconds before the lease parser finished and uploaded the leases.) Therefore I had an out-of-date zone file even though the lease parser had already determined the correct (hostname, ip) mapping, and that mapping was shown in the UI. (Workaround: `service maas-regiond restart`.)
To prevent the possibility of stale leases remaining in the StaticIPAddress table as DISCOVERED, an additional fix was needed to filter stale leases (in case an IP address was assigned to another host).
One issue remains that I found in testing: after the lease parser runs, the zone file isn't udpated. (Rather, I saw it get updated ~3 seconds before the lease parser finished and uploaded the leases.) Therefore I had an out-of-date zone file even though the lease parser had already determined the correct (hostname, ip) mapping, and that mapping was shown in the UI. (Workaround: `service maas-regiond restart`.)