No static IP address / DNS record allocated to a deployed machine after commissioning

[Andres Rodriguez]

In the CI, after the machine successfully finished commissioning, the outpu of the interfaces was the following:

00:e0:81:dd:d5:99 (PXE) 10.245.136.18 (dynamic) maas-eth1 (10.245.136.0/21)
00:e0:81:dd:d5:9a 10.245.136.29 (dynamic) maas-eth1 (10.245.136.0/21)

Right after that, juju deployed the machine, and the machine was never assigned an static IP address. After deployment, we contoinue to see:

00:e0:81:dd:d5:99 (PXE) 10.245.136.18 (dynamic) maas-eth1 (10.245.136.0/21)
00:e0:81:dd:d5:9a 10.245.136.29 (dynamic) maas-eth1 (10.245.136.0/21)

Aug 19 02:37:51 autopkgtest maas.node: [INFO] reasonable-turkey: storage layout was set to lvm. [1/331]
Aug 19 02:37:51 autopkgtest maas.node: [INFO] reasonable-turkey: Status transition from READY to ALLOCATED
Aug 19 02:37:51 autopkgtest maas.node: [INFO] reasonable-turkey: allocated to user admin
Aug 19 02:37:52 autopkgtest maas.node: [INFO] reasonable-turkey: Status transition from ALLOCATED to DEPLOYING
Aug 19 02:37:52 autopkgtest maas.power: [INFO] Changing power state (on) of node: reasonable-turkey (node-0bb87e72-463c-11e5-9383-deadbeef6bb3)
Aug 19 02:37:57 autopkgtest maas.power: [INFO] Changed power state (on) of node: reasonable-turkey (node-0bb87e72-463c-11e5-9383-deadbeef6bb3)
Aug 19 02:38:45 autopkgtest dhcpd: DHCPDISCOVER from 00:e0:81:dd:d5:99 via eth1
Aug 19 02:38:46 autopkgtest dhcpd: DHCPOFFER on 10.245.136.18 to 00:e0:81:dd:d5:99 via eth1
Aug 19 02:38:49 autopkgtest dhcpd: DHCPREQUEST for 10.245.136.18 (10.245.136.6) from 00:e0:81:dd:d5:99 via eth1
Aug 19 02:38:49 autopkgtest dhcpd: DHCPACK on 10.245.136.18 to 00:e0:81:dd:d5:99 via eth1
Aug 19 02:39:37 autopkgtest dhcpd: DHCPDISCOVER from 00:e0:81:dd:d5:99 via eth1
Aug 19 02:39:37 autopkgtest dhcpd: DHCPOFFER on 10.245.136.18 to 00:e0:81:dd:d5:99 (reasonable-turkey) via eth1
Aug 19 02:39:37 autopkgtest dhcpd: DHCPREQUEST for 10.245.136.18 (10.245.136.6) from 00:e0:81:dd:d5:99 (reasonable-turkey) via eth1
Aug 19 02:39:37 autopkgtest dhcpd: DHCPACK on 10.245.136.18 to 00:e0:81:dd:d5:99 (reasonable-turkey) via eth1

This is apparently causing juju to fail because no DNS static record is added.

lease 10.245.136.18 {
  starts 3 2015/08/19 06:39:37;
  ends 3 2015/08/19 18:39:37;
  cltt 3 2015/08/19 06:39:37;
  binding state active;
  next binding state free;
  rewind binding state free;
  hardware ethernet 00:e0:81:dd:d5:99;
  client-hostname "reasonable-turkey";
}

ubuntu@autopkgtest:/var/lib/maas/dhcp⟫ cat /etc/bind/maas/zone.245.10.in-addr.arpa
; Zone file modified: 2015-08-19 02:32:31.573721.
; Note that the modification time of this file doesn't reflect
; the actual modification time. MAAS controls the modification time
; of this file to be able to force the zone to be reloaded by BIND.
$TTL 300
@ IN SOA maas. nobody.example.com. (
              0000000005 ; serial
              600 ; Refresh
              1800 ; Retry
              604800 ; Expire
              300 ; TTL
              )

    IN NS maas.
$GENERATE 10-200 $.136.245.10.in-addr.arpa. IN PTR 10-245-136-$.maas.

[Andres Rodriguez (andreserl)]

I've re-verified and this seems to be the reason why the CI is failing.