[00:14] Hey guys, I have a maas with a couple of nodes virtualized in KVM (I am using them for bootstrap and Neutron) The nodes are reporting they only have 1.44G even though they have a 100G drive specified. Anybody know what;s going on with this? [00:34] nordge1: I think MAAS gets that disk size info from lshw. Go to the node page and check the virtual-disk section of the 00-maas-01-lshw file in the commissioning output. [00:35] or check the Discovery data. [00:37] Ya I see it as 1.44 gb but I need it to shoe the specified size for the openstack installer to clear the requirements for install. I need it to say at least 20 gb [00:38] I wonder If I can just change it by editing the node [00:38] I will try that and let you know [00:39] yes that worked, thanks guys. I guess I just neede to talk it through [12:03] morning [12:46] Is anyone running a MAAS controller inside an LXC container? [12:47] Better: is anyone able to build MAAS from source inside an LXC container? [13:02] rbanffy, it should work just fine; by build I assume you mean "create a package"? [13:02] rbanffy, or run? [13:03] kiko, right now, make install_dependencies is failing [13:05] kiko, libpam-systemd fails to install [13:05] rbanffy, and why? [13:06] kiko, during the install, it tries to connect to the upstart socket [13:07] I'll rerun it and paste a full transcript in a couple minutes [13:11] interesting [14:07] kiko, this time it got stuck at http://pastebin.com/QVF0nej7 [14:28] rbanffy, stuck on.. setting up tgt? [14:28] Yup. Restarted and, this time, it seemed to work. [14:28] Something *very* weird going on [14:46] kiko, some errors, some failures, but the environment now makes sense. Which is weird, because nothing changed http://pastebin.com/2McbgFGg [17:21] newell, ping? [17:21] kiko, pong [17:22] newell, we had a report similar to https://bugs.launchpad.net/maas/+bug/1395896 here yesterday from johng [17:22] Launchpad bug 1395896 in MAAS "Raises CannotConfigureDHCP when saving managedcluster interface." [Critical,Triaged] [17:22] newell, did you ever find a way to reproduce this? [17:22] and do you know what that installation had that was special? [17:22] kiko, no I don't. I will spend some time today trying to install that same branch revision I had when I saw the error. [17:23] To see if I can reproduce it [17:23] newell, no need -- let's see if it comes up again [17:23] kiko, ack [17:27] newell, I was just curious because I've been unable to reproduce myself and johng reported on 1.7.1 [17:29] kiko, yeah understand. If you want me to spend some time trying to reproduce that today I can. [17:29] newell, nah, let's get the amt and pdu stuff moving, more important [17:29] newell, there are some hints in the bug report, I need to investigate === liam_ is now known as Guest13534 [17:31] ack === roadmr is now known as roadmr_afk === roadmr_afk is now known as roadmr [18:10] newell, basically you had a damaged dhcp config [18:11] not sure how you got to it, but it would have required syslog [18:11] and by damaged I mean not just syntax error, but perhaps wrong addresses in there [18:11] kiko: my guess is that his interfaces wasn't configured [18:11] yes [18:12] roaksoax, but I have seen that happen to me before and I didn't get that crash IIRC [18:12] anyway, you are right [18:12] we should fix https://bugs.launchpad.net/maas/+bug/1361673 to avoid this being such a black hole [18:12] Launchpad bug 1361673 in MAAS "CannotConfigureDHCP not handled" [High,Triaged] === roadmr is now known as roadmr_afk === liam_ is now known as Guest73606 === roadmr_afk is now known as roadmr [22:10] Having a problem with tftp -- here's the tracedump from /var/log/maas/pserv.log https://gist.github.com/esacteksab/4adef2ac388841017bb8 [22:10] Using maas 1.7.0+bzr3299-0ubuntu3~trusty1 [22:17] https://bugs.launchpad.net/maas/+bug/1374233 [22:17] Launchpad bug 1374233 in MAAS "pserv continually failing: address already in use" [Critical,Incomplete] [22:23] Upgrading to 1.7.1 and seeing how things work themselves out.