[00:14] <nordge1> 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] <catbus1> 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] <catbus1> or check the Discovery data.
[00:37] <nordge1> 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] <nordge1> I wonder If I can just change it by editing the node
[00:38] <nordge1> I will try that and let you know
[00:39] <nordge1> yes that worked, thanks guys. I guess I just neede to talk it through
[12:03] <kiko> morning
[12:46] <rbanffy> Is anyone running a MAAS controller inside an LXC container?
[12:47] <rbanffy> Better: is anyone able to build MAAS from source inside an LXC container?
[13:02] <kiko> rbanffy, it should work just fine; by build I assume you mean "create a package"?
[13:02] <kiko> rbanffy, or run?
[13:03] <rbanffy> kiko, right now, make install_dependencies is failing
[13:05] <rbanffy> kiko, libpam-systemd fails to install
[13:05] <kiko> rbanffy, and why?
[13:06] <rbanffy> kiko, during the install, it tries to connect to the upstart socket
[13:07] <rbanffy> I'll rerun it and paste a full transcript in a couple minutes
[13:11] <kiko> interesting
[14:07] <rbanffy> kiko, this time it got stuck at http://pastebin.com/QVF0nej7
[14:28] <kiko> rbanffy, stuck on.. setting up tgt?
[14:28] <rbanffy> Yup. Restarted and, this time, it seemed to work.
[14:28] <rbanffy> Something *very* weird going on
[14:46] <rbanffy> kiko, some errors, some failures, but the environment now makes sense. Which is weird, because nothing changed http://pastebin.com/2McbgFGg
[17:21] <kiko> newell, ping?
[17:21] <newell> kiko, pong
[17:22] <kiko> newell, we had a report similar to https://bugs.launchpad.net/maas/+bug/1395896 here yesterday from johng
[17:22] <kiko> newell, did you ever find a way to reproduce this?
[17:22] <kiko> and do you know what that installation had that was special?
[17:22] <newell> 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] <newell> To see if I can reproduce it
[17:23] <kiko> newell, no need -- let's see if it comes up again
[17:23] <newell> kiko, ack
[17:27] <kiko> newell, I was just curious because I've been unable to reproduce myself and johng reported on 1.7.1
[17:29] <newell> kiko, yeah understand.  If you want me to spend some time trying to reproduce that today I can.
[17:29] <kiko> newell, nah, let's get the amt and pdu stuff moving, more important
[17:29] <kiko> newell, there are some hints in the bug report, I need to investigate
[17:31] <newell> ack
[18:10] <kiko> newell, basically you had a damaged dhcp config
[18:11] <kiko> not sure how you got to it, but it would have required syslog
[18:11] <kiko> and by damaged I mean not just syntax error, but perhaps wrong addresses in there
[18:11] <roaksoax> kiko: my guess is that his interfaces wasn't configured
[18:11] <kiko> yes
[18:12] <kiko> roaksoax, but I have seen that happen to me before and I didn't get that crash IIRC
[18:12] <kiko> anyway, you are right
[18:12] <kiko> we should fix https://bugs.launchpad.net/maas/+bug/1361673 to avoid this being such a black hole
[22:10] <bmorriso> Having a problem with tftp -- here's the tracedump from /var/log/maas/pserv.log https://gist.github.com/esacteksab/4adef2ac388841017bb8
[22:10] <bmorriso> Using  maas                                1.7.0+bzr3299-0ubuntu3~trusty1
[22:17] <catbus1> https://bugs.launchpad.net/maas/+bug/1374233
[22:23] <bmorriso> Upgrading to 1.7.1 and seeing how things work themselves out.