[01:54] xygnal: if they are deployed, and the machine is manually configured to pxe boot by default, the machine will PXE boot and will be told to oot from local disk [01:54] xygnal: that sad, the machine should still be dhcp'ing from the hostmap [01:55] xygnal: as mpontillo explained... [01:55] roaksoax the problem appears to be that the host map is not being created [01:55] i've just re-comissioned two machines and tried them with auto-assign, still doing this. going to delete from MAAS all together next. [01:56] xygnal: are there any error logs ? (tail -f /var/log/maas/*.log) [01:58] xygnal: can you 'deploy' a machine, while tailing /var/log/maas/*.log [01:58] xygnal: and share that [01:58] xygnal: also share the output of /var/lib/maas/dhcpd.conf after the machine has been deployed [01:58] err [01:58] after you click deploy and the logs show that the deployment has started [01:58] you will see something like: Apr 27 01:57:27 xenial-maas22 maas.interface: [info] Allocated automatic IP address 192.168.10.109 for eno1 (physical) on apt-heron. [02:00] yes i always see that [02:00] never throws an error either [02:01] and in the UI it shows the auto-asssignend IP [02:01] just dhcpd.conf which is missing the hostmap [02:02] there is only one such angry in there now for a node, and it is for a node i did not build. all of the nodes I have tried to build (with identical config) dont end up with a hostmap [02:04] it's as if the DHCP sync is not happeningning [03:41] xygnal: can you please share your config? [03:41] dhcpd.conf that is [03:56] roaksoax: after moving my dhcpd.conf to a backup and restarting maas-rackd and maas-dhcpd, a new config has written, and it has the missing host mapping. [04:05] roaksoax: and after that, it just booted up with its assigned IP address. [04:05] (thumbsup) [04:17] confirmed on a couple more - all green [04:17] updated the bug report [07:12] Bug #1686607 opened: maas gui doesn't show bond details nor allow editing [08:09] Bug #1686607 changed: maas gui doesn't show bond details nor allow editing === frankban|afk is now known as frankban [10:45] Bug #1686669 opened: MAAS fails to deploy Ubuntu on host that had CentOS deployed and vice-versa [10:45] Bug #1686678 opened: No obvious way to change the domain of a controller [12:03] Bug #1616231 changed: Can't select partition table (MBR vs GPT) [12:13] Bug #1616231 opened: Can't select partition table (MBR vs GPT) [12:22] Bug #1616231 changed: Can't select partition table (MBR vs GPT) [12:34] Hi, can someone can provide me some information about "node-results" cli sub command ? i woud like to have the commisioning summary, but i can not find how to filter it from all the output (i can not find anything on that subcommand under maas doc) [13:32] David_Orange: maas admin node-results read system_id=qctf8r name=00-maas-01-lshw [13:32] that's an example [13:32] obtaining the 00-maas-01-lshw file for the system qctf8r [13:33] David_Orange: http://pastebin.ubuntu.com/24466683/ -> all the commissioning scripts/test scripts (this is maas 2.2) [13:39] roaksoax: Ok, got it, it is files from "commisioning output", i was searching in summary. Thanks a lot [13:42] David_Orange: cool, note that the 'data' field has the data in base64 [13:43] David_Orange: and the summary is just a nice way to show the output from the lshw script + the lldp output one [13:50] roaksoax: ok, got it, thx [14:04] Bug #1686732 opened: [2.2] Cannot release a DISCOVERED IP address [14:10] Bug #1686732 changed: [2.2] Cannot release a DISCOVERED IP address [14:13] Bug #1686732 opened: [2.2] Cannot release a DISCOVERED IP address [14:13] Bug #1686736 opened: [2.2] DISCOVERED IP addresses should never exist outside of the dynamic range [14:19] Bug #1686736 changed: [2.2] DISCOVERED IP addresses should never exist outside of the dynamic range [14:31] roaksoax: hm. this dhcpd.conf not updating strangeness is happening again. had to remove dhcpd.conf, and restart maas-rackd to re-write it. [14:31] roaksoax: a simple diff between the old and new file shows the missing host maps again [14:32] roaksoax how does maas update dhcpd.conf? does it use API commands to add and remove things, or does it just re-write the config and HUP? [14:33] xygnal: rewrites the whole config? are you still using multiople rack controllers ? [14:33] xygnal: and in relay ? [14:33] xygnal: i've been playing around (without relay or HA), and hostmaps get created just fine [14:33] roaksoax: i turned the HA secondary back on, but that side is not running DHCPd [14:34] roaksoax: it never was [14:34] Bug #1686736 opened: [2.2] DISCOVERED IP addresses should never exist outside of the dynamic range [14:34] roaksoax still doing the same thing as before yes. [14:37] blake_r: ^^ why would maas not create the hostmaps [14:38] it does if i remove dhcpd.conf and restart maas-rackd [14:38] blake_r: he is using dhcp relay [14:38] but not before [14:38] xygnal: right, so rackd is nto writing the hostmaps for some reason [14:38] xygnal: so if you removed dhcpd.conf, restarted maas-rackd, and deploy new machines, hostmaps are created just fine ? [14:38] xygnal: is it not writing hostmaps for the relayed vlan? [14:39] xygnal: but it writes hostmaps for the main vlan? [14:39] not exactly. [14:39] everything i deployed is missing hostmaps [14:39] if i delete the conf and restart [14:39] the new conf has those hostmaps [14:39] but any new deploys after that are missinh [14:39] until i repeat the delete and restart [14:39] xygnal: okay let me test on my side without dhcp relay, and see if i am getting hostmaps one moment [14:47] blake_r i've not tried to write maps for the local network, as there are no servers in that. All of our deploying nodes are in relayed fabrics, as that is what the prod arch will be. [14:48] xygnal: yeah I would bet that is the issue [14:48] xygnal: I am going to verify the local, and then I will file a bug, and get you a fix [14:52] xygnal: yep that is the issue [14:56] blake_r: ty sir [14:57] xygnal: thanks for testing DHCP relay! [14:58] blake_r: two way street, your quick help makes a big difference [14:59] xygnal: https://bugs.launchpad.net/maas/+bug/1686755 [15:04] Bug #1686755 opened: [2.2] Relay'd VLAN's hostmaps are not writtin to the dhcpd.conf, unless rackd is restarted [15:22] Bug #1686757 opened: [2.2] Rack registration fails if machine has domain in hostname [15:31] Bug #1686757 changed: [2.2] Rack registration fails if machine has domain in hostname [15:34] Bug #1686757 opened: [2.2] Rack registration fails if machine has domain in hostname [15:34] Bug #1686763 opened: MAAS blanks out search query [15:40] Bug #1686763 changed: MAAS blanks out search query [15:52] Bug #1686763 opened: [2.2, UI] MAAS blanks out search query [16:04] Bug # changed: 1377335, 1393936, 1654063, 1672327, 1672363, 1677056, 1680086, 1680886, 1680979, 1681390, 1681407, 1681442, 1681745, 1681869, 1681937, 1682174, 1682663, 1683433, 1683440, 1683448, 1683502, 1683503, 1683542, 1683855, 1684074, 1684305, 1685306, 1685361, 1685410, 1685435, 1685624, [16:04] 1685835, 1685891, 1685904, 1685955, 1685963, 1686516 [16:43] Bug #1639332 changed: [2.2] Expire the DHCP lease after commissioning or make the default-lease-time configurable [16:43] Bug #1683919 changed: NVMe disk with trusty and hwe-t kernel fails installation [16:52] Bug #1639332 opened: [2.2] Expire the DHCP lease after commissioning or make the default-lease-time configurable [16:52] Bug #1683919 opened: NVMe disk with trusty and hwe-t kernel fails installation [16:55] Bug #1639332 changed: [2.2] Expire the DHCP lease after commissioning or make the default-lease-time configurable [16:55] Bug #1683919 changed: NVMe disk with trusty and hwe-t kernel fails installation [17:25] Bug #1686794 opened: Cancel button broken on add user page === frankban is now known as frankban|afk === mup_ is now known as mup === mimizone_ is now known as mimizone [22:37] Bug #1624344 opened: [2.1] Can't SSH to machine in Rescue mode [22:43] Bug #1624344 changed: [2.1] Can't SSH to machine in Rescue mode