[02:43] any suggestions on how to troubleshoot TFTP timeouts? I have already booted the node using a live CD to check that it can access both the rack and region controller IPs [02:50] does the box get an IP and then fail fetching the image? or does it never get an IP? [02:50] fails to get the image [02:51] Specific error being PXE-E32: TFTP open timeout [02:54] can that box get to the tftp server on the proper port and udp? [02:55] simple telnet test? [02:57] I'm not sure telnet can do udp, nc -u should do it [02:57] doh! why can I never remember nc [02:59] might be hitting a weird VirtualBox issue cause neither the node or the rack controller can [02:59] it just hangs with no output [02:59] that's not abnormal [02:59] it would throw an error if there was a timeout [03:00] hmmm [03:03] so you are saying it is at least responding right, right? [03:04] sounds like it to me [03:17] question then becomes which log to watch [03:28] for instance I don't even see a pserv log in /var/log/maas [03:45] well now I know for sure that the ftp server is working correctly: [03:45] tftp> get /pxelinux.0 [03:45] Received 43395 bytes in 0.0 seconds [05:09] figured it out :-/ [05:12] but now I am hitting an isscsistart issue :-/ [12:46] Bug #1652294 opened: [Device Discovery] The users misunderstand the field Parent to be the machine/device they are adding an interface to [12:46] Bug #1652297 opened: [Device Discovery] When adding a device, the field IP assignment is confusing for the users. They are confused by who is providing DHCP [12:46] Bug #1652298 opened: [Device Discovery] The table is laggy and hard to interact for a large number of discovered devices [12:52] Bug #1652294 changed: [Device Discovery] The users misunderstand the field Parent to be the machine/device they are adding an interface to [12:52] Bug #1652297 changed: [Device Discovery] When adding a device, the field IP assignment is confusing for the users. They are confused by who is providing DHCP [12:52] Bug #1652298 changed: [Device Discovery] The table is laggy and hard to interact for a large number of discovered devices [12:55] Bug # opened: 1652294, 1652297, 1652298, 1652300, 1652301 [13:01] Bug #1652300 changed: [Device discovery] The users had to use the browser search to find devices within the table [13:01] Bug #1652301 changed: [Device Discovery] The users did not see the chevron intended to open the row so they thought they couldn't interact with the table [13:10] Bug #1652300 opened: [Device discovery] The users had to use the browser search to find devices within the table [13:10] Bug #1652301 opened: [Device Discovery] The users did not see the chevron intended to open the row so they thought they couldn't interact with the table [13:22] Does maas also install the nodes over the bmc-interface? Or does it hook on to the ordinary network interface on the node to do the install? [13:26] Bug #1652304 opened: [Device Discovery] The users could not understand what the table and its contents represent [14:17] Bug #1652318 opened: [Device Discovery] The users are unable to see the purpose of this feature [14:17] Bug #1652321 opened: [Device Discovery] The user testing revealed that the users do not understand the concept of devices [20:19] miono: it uses pxe+tftp to do the install [20:20] the bmc/ipmi interface is to set the server into network boot mode and control the power