[13:10] <candyban> Is it me or is MAAS just a POS ? (I just spent 12h getting the damn thing to provision a single machine and it boots with some sort of error). Even the bootstrap of the original machine does not properly work (grub has issue, I have to manually tell grub every time where the root, kernel and initrd is)
[13:11] <candyban> It says it has ssh, but it immediately 'closes connection'
[13:12] <candyban> and I had to click around for ages to get the **** dhcp to provision a machine. (sorry venting here)
[13:14] <candyban> 'worlds best bare metal provisioning tool is quite a stretch imho. I have setup my own pxe systems quicker and easier than this (at least I knew what was going on)
[13:16] <candyban> question: am I doing something wrong or do other people have similar experiences?
[15:07] <kklimonda> you are probably doing something wrong
[15:08] <kklimonda> MAAS has its warts, and lacks documentation, but it's not a POS
[15:52] <ybaumy> kklimonda: i have issues now too. havent changed the setup but now the commissioning fails at boot time with mbr magic error
[19:20] <iggy> candyban: I didn't have any problems
[20:45] <Budgie^Smore> is there a cli way to determine when the first boot image is synced?
[21:51] <pmatulis> kklimonda, what specifically is missing in the documentation?
 It says it has ssh, but it immediately 'closes connection' mine failed to provision and had the same ssh response. Turns out I had set the wrong ip for the region controller. I ran dpkg-reconfigure maas-region-controller and set it to the static IP used on the interface on the network used for PXE booting and it was fine afterwards