[12:48] <mup> Bug #1436826 was opened: Could not start node for commissioning: Node matching query does not exist. <MAAS:In Progress by allenap> <https://launchpad.net/bugs/1436826>
[13:18] <mup> Bug #1436838 was opened: Importing images can fail with "Connection reset by peer" <MAAS:Triaged> <https://launchpad.net/bugs/1436838>
[14:27] <TheMue> heya, I need help with the commissioning of my vMAAS. the VM (VMware with the https://github.com/cloudbase/maas-hacks/tree/master/vmrunapi hack) spins up and boots via PXE
[14:28] <TheMue> but then, after showing a login and the ssh host key fingerprints, it stops
[14:28] <TheMue> maas.log only shows the timeout message
[15:37] <mup> Bug #1436885 was opened: Failure: twisted.internet.defer.CancelledError <twisted> <MAAS:Triaged> <https://launchpad.net/bugs/1436885>
[15:37] <mup> Bug #1436887 was opened: Failure: twisted.web.error.Error: 503 Service Unavailable <twisted> <MAAS:Triaged> <https://launchpad.net/bugs/1436887>
[16:22] <kleemans> This question might be asked previously for a million times, but i've never got a grip on it, how should i setup my ssh key exactly? because i got my maas environment working, can start and stop the nodes, only i can't get ssh connection established from the controller to the node
[16:26] <kiko> kleemans, that's very very odd -- but you're on 1.5 right?
[16:37] <kleemans> i believe the lastest version is 1.7, and i'm running that version, or am missing something?
[16:41] <kiko> kleemans, if you're on 1.7 then you are fine, and I need to understand better what your issue is then
[16:45] <kleemans> what I'm trying to accomplish is to access a node trough ssh from my maas-controller machine
[16:46] <kleemans> because when i try to bootstrap juju, it keeps failing to login to the node
[17:00] <kiko> kleemans, what happens when you ssh -v into the node?
[17:02] <kiko> kleemans, oh, does only the juju ssh fail?
[17:05] <kleemans> kiko, ssh'ing directly into the node doens't work eighter, i'm quickly booting up the node again to test out the ssh -v
[17:05] <kiko> kleemans, that's very strange
[17:05] <kiko> kleemans, so basically none of your nodes are accessible, not via the console or anything?
[17:05] <kiko> that makes maas a bit useless! :)
[17:07] <kiko> kleemans, what exists between the controller machine and the nodes?
[17:07] <kiko> kleemans, a firewall? a switch? something else?
[17:12] <kleemans> only a switch
[17:13] <kleemans> nope, i'm trying to setup a maas environment to test out the juju and eventualy openstack functionality
[17:14] <kleemans> but i'm quite stuck at the accessibility of the nodes ;-)
[17:14] <kleemans> 1 or 2 minutes and the node is running operational
[17:15] <kiko> okay
[17:15] <kiko> look at the console and see if there are any errors reported
[17:18] <kiko> during installation
[17:18] <kiko> kleemans, my thinking is there's something wrong with your keys or the installation
[17:18] <kiko> i.e. the install does not complete successfully but we don't notice it
[17:26] <kleemans> well i believe it might be something with my keys, because i'm not exactly sure how to configure the keys correctly :-)
[17:26] <kiko> lol
[17:26] <kiko> but it should be simple -- you just want to give maas your .pub
[17:28] <kleemans> i just did the ssh -v root@10.0.80.34(nodes ip)
[17:28] <kleemans> gave me host key verification failed at the end
[17:29] <kleemans> should i paste the whole response in the irc?
[17:30] <kleemans> i get an warning message (remote host identityfication has changed)
[17:33] <kleemans> i believe i'm now in my node
[17:34] <kleemans> i used the root user, and by using your -v argument, something outputted Please login as the user "ubuntu" rather than the user "root"
[17:34] <kiko> it's not root
[17:34] <kleemans> and that did the trick
[17:34] <kiko> yep
[17:34] <kiko> the user is always ubuntu
[17:34] <kiko> okay
[17:34] <kiko> so that is working
[17:34] <kiko> now for juju
[17:34] <kiko> how did you set up your juju environment config?
[17:36] <kleemans> fyi, i've installed the juju-core on the maas controller
[17:36] <kleemans> is that ok?
[17:37] <kiko> yes, that's correct -- from the ppa or 14.04?
[17:37] <kiko> the PPA stable is usually saner
[17:38] <kleemans> trough apt-get on a 14.04
[17:38] <kleemans> so i believe thats the 14.04 then?
[17:39] <kiko> yeah
[17:39] <kiko> use the ppa, hang on
[17:40] <kiko> https://launchpad.net/~juju/+archive/ubuntu/stable
[17:40] <kiko> apt-add-repository pa:juju/stable
[17:40] <kiko> err
[17:40] <kiko> apt-add-repository ppa:juju/stable
[17:40] <kiko> apt-get update
[17:40] <kiko> apt-get install juju-core
[17:40] <kiko> kleemans, and then you just follow https://maas.ubuntu.com/docs/juju-quick-start.html
[17:41] <kleemans> allright, i'll do that
[17:41] <kiko> I'll brb, keep us posted
[17:42] <kleemans> i'll sure do
[18:00] <kleemans> brb aswell
[19:16] <mup> Bug #1437007 was opened: API doesn't allow listing nodes that match a set of tags <oil> <MAAS:New> <https://launchpad.net/bugs/1437007>
[20:07] <mup> Bug #1437024 was opened: Failure to PXE-boot from secondary NIC <uefi> <MAAS:New> <https://launchpad.net/bugs/1437024>
[20:41] <nodtkn> Howdy! I am running maas 1.7.2 and I am able to get a grub prompt after loading bootx64.efi and grubx64.efi.  Anybody have a few minutes to point me in the right direction?
[20:43] <roaksoax> nodtkn: you mean you are trying to install with UEFI
[20:43] <roaksoax> nodtkn: but you get  agrub prompt
[20:43] <nodtkn> that is correct
[20:44] <roaksoax> nodtkn: is this a clean install?
[20:44] <roaksoax> nodtkn: what was the previous maas version you were using?
[20:44] <nodtkn> clean install
[20:44] <nodtkn> running my own isc-dhcp-server
[20:44] <roaksoax> nodtkn: did it use to work with a previous maas or is this the first time?
[20:45] <roaksoax> nodtkn: ah well, that might be the issue then
[20:45] <nodtkn> I have gotten pxe boot to work
[20:45] <nodtkn> but not UEFI
[20:47] <nodtkn> I only see it requesting bootx64.efi and grubx64.efi in /var/log/maas/pserv.log
[20:48] <nodtkn> It is my understanding that grub.cfg would be next on the list to download.
[20:51] <roaksoax> nodtkn: well, we do not officially support running external DHCP, which might be the cause of the issue
[20:51] <roaksoax> nodtkn: are there any logs were it fails to download anything from archive.ubuntu.com?
[20:51] <roaksoax> nodtkn: did you test this previously and it worked?
[20:52] <roaksoax> nodtkn: do you have the latest firmware? sometimes firmware issues can cause this too
[20:53] <nodtkn> I do have the latest firmware
[20:54] <nodtkn> on my dhcp server I responded with the pxe image and I was able to pxe boot and commission a node
[20:54] <roaksoax> nodtkn: do you see a failed installation log in the webui?
[20:57] <nodtkn> roaksoax: I you referring to the latest node events? I do not see an installation log in the webgui.  Where would I find that. Under Nodes.
[20:57] <roaksoax> nodtkn: if the machine is in failed deployment status, there should be a install log
[20:57] <roaksoax> link
[20:57] <roaksoax> in the node details page
[20:59] <nodtkn> roaksoax: ah...I am attempting to add new nodes.  Let me to try to reinstall the node I have already commissioned.
[21:01] <roaksoax> nodtkn: this is how a maas managed dhcpd confgi would look like
[21:44] <mup> Bug #1437059 was opened: Deploy bulk actions needs the ability to specify architecture (so we can select hwe kernel) <MAAS:New> <https://launchpad.net/bugs/1437059>
[21:56] <mup> Bug #1437059 changed: Deploy bulk actions needs the ability to specify architecture (so we can select hwe kernel) <MAAS:New> <https://launchpad.net/bugs/1437059>
[22:02] <mup> Bug #1437059 was opened: Deploy bulk actions needs the ability to specify architecture (so we can select hwe kernel) <MAAS:New> <https://launchpad.net/bugs/1437059>
[23:32] <mup> Bug #1331214 changed: MAAS (amttool) cannot control AMT version > 8 <cts> <power> <server-hwe> <MAAS:Fix Committed by newell-jensen> <MAAS 1.7:Fix Committed by rvb> <maas (Ubuntu):Fix Released> <https://launchpad.net/bugs/1331214>