[01:01] <haasn> maas seems to be having some general difficulties managing qemu VMs via the qemu+ssh power management mode. I can't pinpoint anything specific - but some machines work fine, and others do not in strange reasons (usually “machine gets stuck during some phase of deployment because it never got powered on”)
[01:01] <haasn> I'm testing with identical VMs running on the same host using identical settings - except for the name, which is just vm<id>
[01:01] <haasn> So I have no idea why some would randomly work fine and some would randomly get stuck
[01:01] <haasn> Any ideas what could possibly be going on?
[01:11] <haasn> Running sudo -u maas virsh -c $URL start $NAME (with the values copy/pasted from the maas node config) works..
[01:13] <haasn> It also works if I select the machines manually and choose “power on”
[01:14] <haasn> The power status also seems to not update itself consistently, or at all - usually I have to click on “check now” to get correct readings
[09:06] <Praba> we have installed ubuntu server and installed MAAS then in MAAS we got some problems like the image file is not importing
[09:07] <Praba> Can i get some answers in order to recover my problem
[18:34] <haasn> I get this when trying to import boot images: https://0x0.st/X91.txt
[18:34] <haasn> maas 1.9 running on ubuntu 14.04 LTS inside an LXC container
[18:34] <haasn> ‘loop’ module *is* loaded
[18:36] <haasn> Ah seems like an apparmor thing
[18:42] <haasn> https://bugs.launchpad.net/maas/+bug/1474967 contains a fix in the comments