Lost DNS entries for machines managed by MAAS

[Jonas Wagner]

Hi,

Thanks for the suggestions. Unfortunately, I had no success so far. I've
tried calling maas-dhcp-helper manually, but this seems to have no effect.
I also verified that dhcpd is calling it regularly. From the syslog:

Mar 23 10:48:02 dslab-master dhcpd[2239]: execute_statement argv[0] =
/usr/sbin/maas-dhcp-helper
Mar 23 10:48:02 dslab-master dhcpd[2239]: execute_statement argv[1] = notify
Mar 23 10:48:02 dslab-master dhcpd[2239]: execute_statement argv[2] =
--action
Mar 23 10:48:02 dslab-master dhcpd[2239]: execute_statement argv[3] = commit
Mar 23 10:48:02 dslab-master dhcpd[2239]: execute_statement argv[4] = --mac
Mar 23 10:48:02 dslab-master dhcpd[2239]: execute_statement argv[5] =
0:25:90:95:7f:92
Mar 23 10:48:02 dslab-master dhcpd[2239]: execute_statement argv[6] =
--ip-family
Mar 23 10:48:02 dslab-master dhcpd[2239]: execute_statement argv[7] = ipv4
Mar 23 10:48:02 dslab-master dhcpd[2239]: execute_statement argv[8] = --ip
Mar 23 10:48:02 dslab-master dhcpd[2239]: execute_statement argv[9] =
10.0.10.46
Mar 23 10:48:02 dslab-master dhcpd[2239]: execute_statement argv[10] =
--lease-time
Mar 23 10:48:02 dslab-master dhcpd[2239]: execute_statement argv[11] = 600
Mar 23 10:48:02 dslab-master dhcpd[2239]: execute_statement argv[12] =
--hostname
Mar 23 10:48:02 dslab-master dhcpd[2239]: execute_statement argv[13] = bar
Mar 23 10:48:02 dslab-master dhcpd[2239]: DHCPREQUEST for 10.0.10.46 from
00:25:90:95:7f:92 (bar) via eth1
Mar 23 10:48:02 dslab-master dhcpd[2239]: DHCPACK on 10.0.10.46 to
00:25:90:95:7f:92 (bar) via eth1

Cheers,
Jonas

On Fri, Mar 17, 2017 at 6:12 PM Mike Pontillo <mike.pontillo at canonical.com>
wrote:

> On Fri, Mar 17, 2017 at 2:59 AM, Jonas Wagner <jonas.wagner at epfl.ch>
> wrote:
>
> Any further advice on this issue? I've tried a few more things, but all
> without success:
>
> - Link the nodes' interfaces to a subnet. This doesn't work: Cannot link
> subnet interface because the machine is not Ready or Broken.
>
> - Update the dnsresource corresponding to the node's hostname. Trying the
> command "maas foo dnsresource update 2 ip_address=10.0.10.114". This
> returns "Success" but seems to have no effect.
>
> - Create an ipaddress. Trying the command "maas foo ipaddresses reserve
> ip=10.0.10.114 hostname=bar.maas mac=52:54:00:89:04:fb". This tells me "IP
> address 10.0.10.114 belongs to an existing dynamic range. To reserve this
> IP address, a MAC address is required. (Create a device instead.)"
>
>
> Sorry, I didn't get a chance to look again at this yesterday. I'd need to
> spend some more time digging into this to give you a full answer.
>
> One thing I can suggest for the moment: you could try releasing and
> renewing the DHCP IP address from the deployed server. Doing this might
> cause MAAS to receive the notification from DHCP that a lease has been
> issued, and thus add the system back into DNS. You could try simulating
> this on the MAAS server by calling /usr/sbin/maas-dhcp-helper with the
> correct arguments, such as:
>
> /usr/sbin/maas-dhcp-helper notify --action commit --mac 52:54:00:89:04:fb
> --ip-family ipv4 --ip 10.0.10.114 --hostname bar.maas
>
> Regards,
> Mike
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/maas-devel/attachments/20170323/2d50e794/attachment.html>