[00:21] I found an entry in /usr/lib/python2.7/dist-packages/maasserver/modes/node.py defining commissioning time for 20 minutes, but when I modify it to 40, it still only runs for 20. Am I going in the right direction here? [00:22] sorry, /usr/lib/python2.7/dist-packages/maasserver/models/node.py [01:28] Actually, it might have taken the changes this time. Its been commissioning now for 30 minutes and hasn't timed out yet. I restarted the server after making the change this time and it seems like it is working. [01:34] Sweet! Changing the value in the node.py file adjusted the timeout. The servers are now commissioning properly and going into the Ready state! === ejat_ is now known as ejat [12:13] Bug #1531836 opened: Power state does not show on node using Digital Loggers PDU [12:16] Bug #1531836 changed: Power state does not show on node using Digital Loggers PDU [12:31] Bug #1531836 opened: Power state does not show on node using Digital Loggers PDU [12:41] Bug #1531843 opened: [Xenial 1.10] IPMI query fails <1.10> [13:23] I frequently have trouble enlisting nodes, where it gives me "failed to enlist system maas server 'm2-test1.maas....' [13:24] where the name there matches the last node that I successfully enlisted. [13:24] has anyone seen that? [13:24] AFAICT, it looks like something where when a node boots, it gets an IP address (in this case 200*) which then successfully enlists [13:24] so it gets a DNS address. [13:24] but once that node is successfully in rotation, it gets a different address. [13:25] and then the next node that tries to enlist, gets the same Dynamic DHCP address (which is perfectly fine) [13:25] but DNS still thinks it is the same node [13:25] and it fails [14:12] dimitern: I can confirm that without your patch I couldn't bootstrap, with your patch it works [14:20] Bug #1531868 opened: Add network fails for multiple class B networks [14:23] Bug #1531868 changed: Add network fails for multiple class B networks [14:26] Bug #1531868 opened: Add network fails for multiple class B networks [14:26] jam, awesome! thanks for giving it a go :) [14:29] Bug #1531868 changed: Add network fails for multiple class B networks [14:32] Bug #1531868 opened: Add network fails for multiple class B networks [15:17] Bug #1531836 changed: Power state does not show on node using Digital Loggers PDU [15:17] Bug #1531868 changed: Add network fails for multiple bigger-than-/24 networks in a single /16 [16:02] is there any way for me to tell in logs which preseed files, if any, a host used during commissioning? [16:14] Bug #1531531 changed: 1.9 rc4: third-party driver not getting installed for storage device [16:17] Bug #1531531 opened: 1.9 rc4: third-party driver not getting installed for storage device [16:23] Bug #1531531 changed: 1.9 rc4: third-party driver not getting installed for storage device === racedo is now known as racedo|vodafone === med_` is now known as med_ === med_ is now known as med === med is now known as med_ [18:17] Hi All [18:17] i have a sharp question [18:17] about adding a redhat image [18:58] is there any way for me to tell in logs which preseed files, if any, a host used during commissioning? === CyberJacob_ is now known as Guest58713 === plars_ is now known as plars [19:53] is there a good "block diagram" for maas that indicates the various processes and how they communicate? === wililupy is now known as wililupy|Lunch === wililupy|Lunch is now known as wililupy [20:06] dbainbri: theres this - https://maas.ubuntu.com/docs/orientation.html [20:06] dbainbri: probably not as complete as your looking for though [20:23] ltrager: thx. it is a start. looking to understand how to run maas in a collection of containers. [20:25] does anyone here do anything with curtin preseeds? [23:47] when changes are made to the cluster, maas will update the dhcpd.conf file and restart the dhcpd process (i.e. cause a conf reload). is that accurate?