Comment 42 for bug 1519527

Ok,

After doing some manual testing yesterday, I've been unable to reproduce this bug.

This is what I see in the MAAS logging:

Dec 3 06:56:15 trusty-maas9 maas.api: [INFO] juju-machine-1-lxc-0: Added new device
Dec 3 06:56:15 trusty-maas9 maas.api: [INFO] juju-machine-1-lxc-0: Sticky IP address(es) allocated: 192.168.10.104
Dec 3 06:56:15 trusty-maas9 maas.dns: [INFO] Generating new DNS zone file for maas
Dec 3 06:56:15 trusty-maas9 maas.dns: [INFO] Generating new DNS zone file for 10.168.192.in-addr.arpa
Dec 3 06:57:06 trusty-maas9 maas.import-images: [INFO] Started importing boot images.
Dec 3 06:57:06 trusty-maas9 maas.import-images: [INFO] Finished importing boot images, the region does not have any new images.
Dec 3 06:57:11 trusty-maas9 maas.lease_upload_service: [INFO] Uploading 48 DHCP leases to region controller.
Dec 3 06:59:59 trusty-maas9 maas.api: [INFO] juju-machine-1-lxc-1: Added new device
Dec 3 06:59:59 trusty-maas9 maas.api: [INFO] juju-machine-1-lxc-1: Sticky IP address(es) allocated: 192.168.10.105
Dec 3 06:59:59 trusty-maas9 maas.dns: [INFO] Generating new DNS zone file for maas
Dec 3 06:59:59 trusty-maas9 maas.dns: [INFO] Generating new DNS zone file for 10.168.192.in-addr.arpa
Dec 3 07:00:08 trusty-maas9 maas.api: [INFO] juju-machine-1-lxc-2: Added new device
Dec 3 07:00:08 trusty-maas9 maas.api: [INFO] juju-machine-1-lxc-2: Sticky IP address(es) allocated: 192.168.10.106
Dec 3 07:00:09 trusty-maas9 maas.dns: [INFO] Generating new DNS zone file for maas
Dec 3 07:00:09 trusty-maas9 maas.dns: [INFO] Generating new DNS zone file for 10.168.192.in-addr.arpa

I've verified that the containers get the right IP address and DNS record, and everything works as expected. That being said, this was a 1.9 freshest install and it wasn't an upgrade from 1.8.

We are going to try to reproduce this tomorrow, but in the meantime, I'll mark this bug as incomplete until Ryan can setup his environment all over again and we can work though this.

Thanks.