On Fri, Mar 17, 2017 at 2:59 AM, Jonas Wagner <[email protected]> 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
-- Maas-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/maas-devel
