[03:07] <julianwa> racedo: ping
[04:58] <raywang> bigjools, ping
[04:58] <bigjools> hi raywang
[04:59] <raywang> hi bigjools we are facing a serious problem. When trying to add ssh key into maas, it report "invalid ssh public key"
[04:59] <bigjools> raywang: are you not using juju?
[04:59] <raywang> which we guarantee  the key is no problem (try three times for new keys)
[05:00] <raywang> bigjools, we will use juju, but before that, we are trying to insert public key to maas
[05:00] <bigjools> raywang: you don't need to add a key to maas if you use juju
[05:00] <raywang> bigjools, sorry, I mean "Add SSH Key" to maas
[05:02] <raywang> bigjools, are you saying "there is no need to add ssh key to maas manually? if use juju to deploy services, it will grab the public key, and add it into VM automatically
[05:02] <bigjools> raywang: that's correct
[05:02] <bigjools> the manual ssh key adding is only needed if you plan on using maas to manually start nodes
[05:02] <raywang> bigjools, in other words, if we don't use juju and don add ssh key, how can we login the system without inserting the public key?
[05:03] <bigjools> if you are using juju it just works
[05:03] <raywang> bigjools, does 0.6 version of juju works?
[05:04] <bigjools> if it has maas in it, it should do
[05:04]  * bigjools can't remember juju versions
[05:04] <raywang> ok
[05:04] <raywang> bigjools, i just want to make sure this is the feature of juju go version
[05:05] <bigjools> raywang: yes it wll be the same in Go
[05:05] <raywang> if the case is we start the node manually, so we have to add ssh public key to maas,  and this time we fail to add the key, how can we find out where is the problem? :-)
[05:06] <bigjools> raywang: you can't!
[05:06] <bigjools> it ought to prevent manual startup if there's no ssh key
[05:08] <raywang> bigjools, got it, so anyway to find out why it fail to add the ssh public key?
[05:08] <raywang> any way
[05:08] <bigjools> raywang: which version of maas?
[05:08] <bigjools> and can you paste me the public key string you're trying to add
[05:08] <raywang> maas    1.2+bzr1373+dfsg-0ubuntu1~12.04.1~ppa1
[05:09] <raywang> from ppa:maas-maintainers/stable
[05:09] <bigjools> good :)
[05:09] <julianwa> bigjools:  ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC4SrSolwrO33ZYsRtoMWlouEgVcztNJwdOi1g6MwS3Ihnb9coVnHYMNPeeuj5HLOtJ4obkupAWJcKS/6c26k56V3ry0bILduQatxCb9lHzj
[05:09] <julianwa> Zc2wKm84szcU77pPO4XIloyWPM3GX+xBZb3lj6C6PzvIeMpeXYPa+fIoXwBmKK0ae+P+zK3HBR4AwuuBdgpFzPaB2S2e1phVzocdI7oC38dhOj4GFK2+rcdqPGnlJZp49vGhvftTLNHUU7Wc1
[05:09] <julianwa> V1ydIasO/5+opP+CTqvbx34aec6WN3ASAyiC/QhgP8fLST6LlHqfDAVOUJMKE1f7gWpNcqpBvf768PqxEO0xNemf maasadmin@MAAS-ADMIN
[05:10] <bigjools> ok hang on
[05:11] <raywang> bigjools, ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC4SrSolwrO33ZYsRtoMWlouEgVcztNJwdOi1g6MwS3Ihnb9coVnHYMNPeeuj5HLOtJ4obkupAWJcKS/6c26k56V3ry0bILduQatxCb9lHzjEZc2wKm84szcU77pPO4XIloyWPM3GX+xBZb3lj6C6PzvIeMpeXYPa+fIoXwBmKK0ae+P+zK3HBR4AwuuBdgpFzPaB2S2e1phVzocdI7oC38dhOj4GFK2+rcdqPGnlJZp49vGhvftTLNHUU7Wc14V1ydIasO/5+opP+CTqvbx34aec6WN3ASAyiC/QhgP8fLST6LlHqfDAVOUJMKE1f7gWpNcqpBvf768PqxEO0xNemf maasadmin@MAAS-ADMIN
[05:13] <bigjools> are you pasting it in without line breaks?
[05:13] <bigjools> in maas's dialog
[05:14] <bigjools> because I can add your key into my running maas
[05:14] <bigjools> raywang: ^
[05:15] <raywang> bigjools, yeah, you are probably right, the content we copy from "screen" has line breaks i guess
[05:15] <bigjools> raywang: yes, I could tell from the way  julianwa pasted it :)
[05:15] <raywang> bigjools, great, thank you!
[05:16] <raywang> bigjools, it's great to have you in the same timezone :)
[05:16] <julianwa> bigjools: screen's problem..
[05:16] <bigjools> raywang: easiest way is to "cat ~/.ssh/id_rsa.pub"
[05:16] <bigjools> then copy/paste from that
[05:16] <raywang> bigjools, yes, that's how we did
[05:16] <bigjools> the terminal won't have line breaks
[05:16] <bigjools> cool
[05:17] <bigjools> raywang: glad to help :)
[05:17] <raywang> bigjools, we just  "cat ~/.ssh/id_rsa.pub", and copy from the terminal
[05:17] <raywang> bigjools, maybe 'screen' screw it up
[05:17] <bigjools> quite possible
[05:17] <bigjools> screen generally screws things up
[05:18] <julianwa> you are right.
[07:03] <julianwa> bigjools:  when we using maas to manage vm, it always takes us so long time to wait ipmi while enlist/comissioning/install
[07:04] <bigjools> julianwa: there's a fix coming for that soon
[07:04] <bigjools> it may even be in the daily builds
[07:05] <julianwa> bigjools:  cool.
[11:51] <dragunov11> Am getting the "exceptions.AssertionError: No PXE template found in '/usr/lib/python2.7/dist-packages/provisioningserver/pxe'!" error
[11:51] <dragunov11> even after accepting the nodes for commissioning.
[11:52] <dragunov11> I referred to this https://bugs.launchpad.net/maas/+bug/1064212 . But it happens with me even if the node is in "Ready" state.
[11:53] <dragunov11> Any particular solution guys?
[11:53] <bigjools> the node must be started via MAAS
[11:53] <bigjools> not manually
[11:55] <dragunov11> How do I start the node through MAAS ?
[11:55] <dragunov11> using WoL ?
[11:55] <bigjools> use the button in the UI or preferably connect it to juju
[11:55] <bigjools> once maas thinks the node is starting up, you can start it manually if you want
[11:56] <dragunov11> oh ok.
[11:56] <bigjools> but it's obviously more convenient to have WoL or some other power control
[11:57] <dragunov11> Ok. Going to try it now.
[12:00] <dragunov11> Its working. Thanks bigjools
[12:01] <bigjools> ok