[00:18] kiko: That is not what I am looking for... for Ubuntu, you can have custom preseeds. We need something similar for CentOS as well, without going through the pain of creating custom images... [00:24] alexlist: what are you looking for? [00:27] alexlist: you *can* have custom preseeds for centos [01:47] Bug #1588116 opened: [2.0-bzr5059] Adding a rack using dpkg-reconfigure isn't intuitive [02:44] Bug #1588125 opened: Nodes commission, but don't see network interfaces with Xenial [04:58] Bug #1588154 opened: Deploying node fails when it has VLAN configuration [06:01] Bug #1588161 opened: Empty boot-source-selections imports all available images === frankban|afk is now known as frankban [13:00] Bug #1588350 opened: [2.0b5] Multiple power query's in too little time [13:06] Bug #1588350 changed: [2.0b5] Multiple power query's in too little time [13:12] Bug #1588350 opened: [2.0b5] Multiple power query's in too little time === jgrimm-afk is now known as jgrimm [15:28] alexlist, what roaksoax said -- you can generate custom preseeds for centos; the preseeds are not OS-specific but rather specific to curtin (and cloud-init) [16:00] kiko: /etc/maas/preseeds/curtin_userdata_centos [16:00] alexlist: ^^ [16:00] alexlist: so you can basically do what you need via preseeds [16:05] in maas, can I set the default ipmi credentials? [16:05] somewhere [16:05] rather than waiting to assign it to hosts which are discovered [16:05] I'd prefer it if Maas defaulted to ipmi 2.0 and used N credentials [16:40] gimmic: you can change the credentials after you commission the machine === frankban is now known as frankban|afk [17:02] so I've got a host deployed, but I can't seem to ssh to it with the set key [17:02] actually, status says "deploying" [17:07] gimmic, need to wait until it's deployed [17:07] I can't see any activity on the host or the maas server [17:35] Hi guys, I changed the "external" facing IP of my maas server and now I'm having trouble. I can connect via ssh but dhcpd isn't running and I dns look-ups to external sites fail. Any hints at config I'd have to change? [17:35] maas 2.0 [17:40] ah..nevermind I got it figured out. thanks [17:44] Bug #1588466 opened: gpg --batch --verify during maas install causes Unhandled Error [17:44] Bug #1588469 opened: cluster view won't load if a single cluster controller lacks a valid UUID [17:48] hmm.. I spoke to soon. I fixed the dns lookups but dhcpd is not starting [17:50] I can't seem to find any log files related to maas-dhcpd or dhcp [17:50] any pointers? [18:16] shewless, you may need to do a dpkg-reconfigure -- you used to in 1.9. roaksoax, any clue? [18:27] kiko: thanks - is there harm in my doing that on 2.0.0? [18:28] kiko: also which package would I reconfigure? [18:29] shewless, I'd guess maas-rackd [18:31] shewless: have you tried setting upstream DNS server in MAAS ? [18:33] roaksoax yes I have [18:34] roaksoax: it's set to an internal DNS that is still reachable by ping [18:34] shewless: so why is dhcp not running ? have you looked at systemd ? [18:34] roaksoax: I'm not sure how to do that. [18:36] shewless: journalctl -u maas-dhcpd -> try that ? [18:37] roaksoax: 1 single entry: Jun 02 14:37:22 maas systemd[1]: Stopped MAAS instance of ISC DHCP server for IPv4. [18:37] if I restart the service it just prints that [18:38] shewless: so what if you do ps faux | grep dhcpd ? [18:38] nothin [18:39] roaksoax: that command shows me tthat dhcpd is not running [18:39] shewless: ok, so is DHCP enabled at all in MAAS ? [18:40] roaksoax: yes it is. I tried disabling it and re-enabling it but it didn't seem to have an effect. Related if I do a "service maas-dhcpd status" I see that /var/lib/maas/dhcpd.conf is missing.. that's probably bad right? [18:41] Bug #1588489 opened: package maas-region-controller 2.0.0~beta3+bzr4941-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned [18:41] error exit status 1

[19:33] roaksoax: so any idea why the dhcpd.conf file isn't being generated? Is that rackd that would do that? [19:47] shewless, it's a bug I think -- roaksoax? [19:50] Bug #1532478 changed: Can't add SM15K chassis - can't input management IP address of SM15k [19:52] shewless, can you disable and reenable DHCP management on the vlan you are servicing? [19:52] have you already> [19:52] ? [19:57] trying to troubleshoot maas API with Postman. Anyone able to get this basic GET call to work via Postman? http:///MAAS/api/version [19:57] sjl, I have never tried that -- does Postman do OAuth? [19:58] yes 1.0 and 2.0 [19:58] so when deploying, it installs and ends at "cloud-init finished..." [19:58] but the box stays in "deploying" state [19:59] closer look appears to be "Node installation - 'curtin' failed: configuring disk: sda" [20:00] yep [20:00] why did it fail to configure? [20:01] where can I find relevant log data? [20:01] look through the install log [20:02] shewless: have you enabled DHCP ? [20:02] shewless: MAAS will only generate a dhcpd.conf is DHCP is enabled [20:02] shewless: also, pastbin rackd.log [20:03] wheres the install log located? [20:03] I don't have access to the iron(yet), and don't see anything specific in maas' log [20:05] gimmic, maas sends it back and it gets attached to the node page IIRC [20:05] the node page was where I pulled that from, I don't see any additional detail [20:05] hm [20:05] gimmic, are you doing anything custom to sda? [20:06] and if not, is there anything unusual about it? [20:06] generic out-of-box install [20:06] r620, single SATA [20:07] this will be the second node deployed, the first onedid the same thing until I rebooted it [20:07] I'm obviously trying to streamline it a bit and tshoot things [20:07] but basic 14.04 LTS image, very generic hardware. I have 30 of these nodes to do [20:15] gimmic, it's very odd tbh [20:15] gimmic, so the entire install log has no hints other than the sda failure? can you put it in a pastebin [20:16] anywhere I can view the log in actual raw format [20:16] rather than the weberface [20:16] doesnt seem to be much useful in /var/log/maas [20:18] one other interesting question is that on some nodes I want to use a software raid to mirror two disks [20:18] but since it uses one off the bat, I can't seem to use maas to configure it to mirror the disk [20:20] gimmic, you can just configure the software raid in the MAAS UI itself [20:20] that should be pretty straightforward (and worked as far back as 1.9x) [20:20] but not before the node has been commissioned as far as I can tell [20:21] correct [20:21] the node needs to commission first [20:21] oh [20:21] are you stuck on the commissioning step? [20:21] commissioning has an option you can select to let you log in and inspect [20:21] have you checked that? [20:21] (sorry, I thought you were mid-deployment) [20:23] oh, found it. I'm conflagulating two different 'issues' right now. [20:23] One set of nodes has two disks, and they will be mirrored / [20:23] that I just found under a node that was in ready state [20:23] Can I make templates for this somehow? [20:29] not yet [20:29] gimmic, you will be able to, but for the moment the solution is to script node config via the API [20:35] this is all the detail I can find on the deploy errors: [20:35] Node installation - 'curtin' failed: configuring storage Thu, 02 Jun. 2016 15:23:01 [20:35] Node installation - 'curtin' failed: configuring disk: sda Thu, 02 Jun. 2016 15:23:01 [20:35] Node installation - 'curtin' started: configuring disk: sda Thu, 02 Jun. 2016 15:23:00 [20:35] Node installation - 'curtin' started: configuring storage Thu, 02 Jun. 2016 15:22:59 [20:35] roaksoax: I'll workon getting rackd log. DHCP is enabled as far as the UI tells me.. on my PXE network [20:38] kiko: oddly, if I reboot the node it deploys fine the second time [20:38] so it is something with partition creation or an error in the install/deploy script [20:39] about to test the theory with a third node [20:39] wwird [20:42] Bug #1519358 changed: Non-fatal error message observed in PXE boot sequence [20:42] Bug #1588531 opened: [2.0b5] Deployed regions should be able to transistion back to machines [20:42] roaksoax: here is rackd.log: http://paste.ubuntu.com/16930706. Note: for some reason if resolve.conf points to maas' own DNS server I can't resolve external DNS (like google). DOn't know if that is related [20:51] Jun 2 20:47:59 ES18 [CLOUDINIT] util.py[DEBUG]: Running scripts-user () failed#012Traceback (most recent call last):#012 File "/usr/lib/python2.7/dist-packages/cloudinit/stages.py", line 658, in _run_modules#012 cc.run(run_name, mod.handle, func_args, freq=freq)#012 File "/usr/lib/python2.7/dist-packages/cloudinit/cloud.py", line [20:51] 63, in run#012 return self._runners.run(name, functor, args, freq, clear_on_fail)#012 File "/usr/lib/python2.7/dist-packages/cloudinit/helpers.py", line 197, in run#012 results = functor(*args)#012 File "/usr/lib/python2.7/dist-packages/cloudinit/config/cc_scripts_user.py", line 38, in handle#012 util.runparts(runparts_path)#012 File "/usr/lib/python2.7/dist-packages/cloudinit/util.py", line 651, in runparts#012 % (len(failed), len( [20:51] attempted)))#012RuntimeError: Runparts: 1 failures in 1 attempted commands [20:53] small ui bug during deployment: https://i.imgur.com/RgPKPSq.png [20:54] system is ON, dropdown option is 'turn system on' which actually turns it off.. [20:56] roaksoax/kiko: I tried to disable DHCP on all networks. I deleted the subnet entirely and then I re-added the subnet and re-enabled DHCP.. dhcpd still won't start because that file is missing [20:56] what service is responsible for creating dhcpd.conf? I don't see any logs that indicate a problem there [20:56] shewless, rackd does [20:57] kiko: okay.. rackd doesn't want to tell me about any errors regarding dhcpd.conf I guess :( [20:57] shewless, it seems to be confused about the IP address it needs to be listening on? [20:58] kiko: interesting.. that might be the hint I needed [20:59] /wg 6 [21:00] kiko: so.. regiond.conf should be the "pxe" IP address right? [21:00] kiko: It's working now.. I had it set to my external IP address instead somehow [21:00] anyways.. dhcpd is running.. that's a good first step [21:02] shewless, you have a single node running both rackd and regiond right? [21:03] kiko: yup. and I think it's all working now (hopefully) just going to test deployment now [21:04] shewless, cool [21:05] shewless, this is an old bug, btw, that changing the MAAS server's IP address causes a mess [21:05] gimmic, hmm [21:06] testing a theory, I changed the default filesystem to use LVM instead of flat [21:06] we'll see if deploys still err [21:06] i set one to allow ssh and got in to look [21:06] everything looks fine aside from that error I posted [21:06] seems if I deploy the same node twice, it deploys fine the second time [21:12] the raided node deployed fine [21:51] Bug #1523766 changed: Node stops commissioning and powers down before commissioning is complete [22:21] Bug #1588547 opened: Generated bonding configuration is incorrect. [22:48] Bug #1588547 changed: Generated bonding configuration is incorrect. [23:46] Bug #1588547 opened: Generated bonding configuration is incorrect.