[01:44] <bigjools> roaksoax: don't suppose you're about?
[01:44] <bigjools> squashfs is too buggy so I want to remove it
[01:49] <lifeless> what sort of bugs ?
[01:49]  * lifeless is curious
[01:56] <bigjools> lifeless: bug 1076409, bug 1074167, bug 1077180 for starters
[01:56] <bigjools> lifeless: maas-specific stuff :)
[01:57] <lifeless> fun
[15:04] <gwd> So I've been trying to follow the instructions for setting up MaaS from here: https://maas.ubuntu.com/docs/install.html
[15:06] <gwd> And it seems that although the machine acting as both region and cluster controller is quantal (12.10), "maas-import-pxe-files" only grabs precise.  That seems a bit unexpected. :-)
[15:26] <gwd> smoser: I'm starting to look at writing a Xen / XCP charm you can use for your OpenStack testing.  Is there a KVM/libvirt charm I can use as a sort of template?  I don't see one in the "Charm Store", or in the examples that come in the quantal juju package.
[15:29] <smoser> gwd, :-( maas-import-pxe-files  is actually busted at the moment. (bug 1074167)
[15:29] <smoser> i'll walk through and get you a workaround to get quantal
[15:29] <smoser> (it just wont use the squashfs based install, but the end should be the same)
[15:30] <gwd> smoser: I edited /etc/maas/import_pxe_files to include both precise and quantal, that seemed to work OK...
[15:30] <smoser> oh?
[15:30] <smoser> i would have thought it woudl faail if you did that.
[15:30] <smoser> (failing to get the squashfs image)
[15:30] <smoser> but if it works, thats good enough.
[15:30] <gwd> Well as you say, the squashfs / ephermeral stuff fails, but the normal ones seem to be working ok...
[15:31] <smoser> and install works? thats good enough then.
[15:32] <smoser> for "kvm/libvirt charm". the charms that we use to deploy openstack ... i'm looking
[15:34] <gwd> Hmm -- I set up some VMs with a private network, so that I could run dhcp / pxeboot without bothering our IT guys, but a lot of aspects of the maas / juju setup seem to assume this is not the case.  For instance, "juju status" is complaining that it can't resolve hostname u1.
[15:34] <smoser> http://bazaar.launchpad.net/~gandelman-a/+junk/juju-deployer/files is the "deployer"
[15:35] <smoser> ping adam_g or jamespage in #ubuntu-server for more info
[15:35] <smoser> i'd have to dig, and they cna probably give you better reference.
[15:35] <smoser> join there, i'll introduce
[15:44] <gwd> smoser: Thanks for the intro.  Back to maas -- "juju bootstrap" has produced an installed a juju controller, but "juju status" reports "ERROR Invalid SSH key".  Is there a default login that I can use to log into the controller and see what's going on?
[15:45] <smoser> gwd, if you cannot get in to the installed node, then something is busted. :-(
[15:45] <smoser> are you able to see console logs on that system?
[15:47] <gwd> smoser: You mean serial output or something like that?  No -- unfortunately it's actually a VM. :-/  Is that information available from the maas controller anywhere?
[15:48] <smoser> gwd, wel, you shoudl actually get syslog installer info back to the maas controller
[15:49] <smoser> in /var/log/maas/rsyslog ... or somewhere down there.
[15:49] <smoser> for debugging at this point you need to set a password for the user and just login and then poke around.
[15:49] <smoser> (you could boot with init=/bin/bash or we can modify the preseed to the installer)
[15:50] <smoser> i'm really, really sorry you have an issue.
[15:50] <smoser> you imported your ssh keys ?
[15:50] <smoser> to maas?
[15:51] <gwd> smoser: I'm not too frustrated yet -- it's somewhat different than what I normally work on, so it's somewhat interesting. :-)
[15:51] <gwd> smoser: I did have 2 ssh keys I put into the web UI -- maybe the fact that there was 2 is the problem?
[15:53] <gwd> smoser: MaaS seems a bit confused at my setup as well -- the machines being controlled are on their own private sub-net, and NAT'ed through the controller.  I had to do some massaging of the configuration files to get pxeboot to work right, for instance.
[15:55] <gwd> smoser: So I found the rsyslog files for my juju controller on the maas controller -- anything in particular I should be looking for?
[15:58] <smoser> gwd, so the install generally worked?
[15:58] <smoser> the system?
[15:58] <smoser> hm.
[15:58] <gwd> smoser: So it would seem -- I've got a machine (u1) that went through the install process, and gives me a login at the console.
[15:59] <gwd> smoser: And I can see the install logs on the maas controller (hostname maas), but I don't see anything in the logs about installing ssh keys.
[16:00] <smoser> right.
[16:00] <smoser> that happens on first boot.
[16:00] <smoser> i assume something is breaking, and cloud-init on the installed node did not get the metadata from MAAS
[16:00] <smoser> (which is how the keys wouldget pulled in)
[16:01] <smoser> so... we can change the maas server preseed for the install
[16:01] <smoser> so that it creates a user with a password
[16:02] <gwd> Right -- where is that, and how can I trigger a re-install?
[16:04]  * gwd goes afk for a few minutes
[16:11] <smoser> gwd, juju destroy-environment
[16:11] <smoser> and juju boostrap willd o it
[16:14] <gwd> smoser: OK cool; how about adding a password to the default user?
[16:16] <smoser> riight.
[16:16] <smoser> oh shoot.
[16:16] <smoser> did i not paste that.
[16:16] <smoser> somewhere there is a preseed file.. ( i dont have it in front of me, ,and i'm trying to juggle too many things right now)
[16:16] <smoser> but you want to basically do:
[16:16] <smoser> d-i   passwd/root-login boolean false
[16:16] <smoser> d-i   passwd/make-user  boolean true
[16:16] <smoser> d-i   passwd/user-fullname string ubuntu
[16:16] <smoser> d-i   passwd/username   string ubuntu
[16:16] <smoser> d-i   passwd/user-password-crypted  password $6$.1eHH0iY$ArGzKX2YeQ3G6U.mlOO3A.NaL22Ewgz8Fi4qqz.Ns7EMKjEJRIW2Pm/TikDptZpuu7I92frytmk5YeL.9fRY4.
[16:16] <smoser> d-i   passwd/user-uid   string
[16:17] <smoser> (some of that is already there)
[16:17] <smoser> you just want to add the password-crypted field
[16:17] <smoser> and that string is "ubuntu"
[16:17] <gwd> OK -- I'll look around for it.
[17:57] <gwd> smoser: So it appears that there was a race between /home being mounted and the ssh keys being installed.
[17:57] <smoser> separate home partition?
[17:57] <gwd> smoser: The installer creates xvda1 to mount on /, and xvda6 to mount on /home.
[17:57] <smoser> i'll admit i've never considerd that.
[17:58] <smoser> hm..
[17:58] <gwd> smoser: xvda1 has /home/ubuntu/.ssh with the proper keys in it; but while xvda6 has ubuntu/, it doesn't have any ssh configs.
[17:59] <smoser> gwd, its not a race
[17:59] <smoser> i think you're actually guaranteed failure :)
[17:59]  * gwd was being optimistic. :-)
[18:00] <smoser> this is interesting.
[18:00] <smoser> the auto partitioner chose to give you a /home. i dont think i'd seen that before.
[18:02] <smoser> Daviey, ^ that is interesting in maas.
[18:02] <gwd> smoser: So a work-around might be to add the following line: d-i partman-auto/choose_recipe select atomic
[18:04] <smoser> i dont know. its wierd to me that it did that.
[18:04] <smoser> so, since hte other wierd thing is xen, i suspect somethign related to xen
[18:04] <smoser> :)
[18:15] <gwd> smoser: Very weird... even with the preseed line I wrote above, it still made a /home partition. :-/  This is all with quantal.
[18:17] <smoser> gwd, well, i think we can work around this.
[18:17] <smoser> but it sucks.
[18:17] <smoser> it will require you to do a late_commadn to edit /etc/cloud/cloud-init.cfg
[18:20] <smoser> we basically ahve to apply this patch i think
[18:20] <smoser> http://paste.ubuntu.com/1353734/
[18:23] <Daviey> smoser: eww
[18:24] <Daviey> smoser: i had not seen that before ether.. Is it anew default in debian?
[18:24] <smoser> he's just using quantal
[18:26] <Daviey> smoser: right, but i wondered if debian had started doing it, and we are getting it 'for free' as part of d-i?
[18:29] <gwd> smoser,Daviey: Well to compare, my maas controller VM was installed via mini.iso -> network install; so it 1) booted under xen but 2) only created one partition
[18:29] <gwd> Anyway, I've got to head out here -- thanks for your help, smoser.  Hopefully tomorrow things will go smoother. :-)
[18:29] <Daviey> gwd: right, but wasn't preseeded i am assuming ?
[18:29] <gwd> Daviey: That's right.
[18:30] <Daviey> gwd: yeah, i'm wondering if preseeded installs generally have different behaviour
[18:30] <Daviey> i don't think this is a maas bug, as such... more of a di one..  but that is nothing more than a hunch, with no facts to indicate it :)
[18:32] <gwd> Daviey: The Ians here on the Xen team know a bit about Debian; I'll ask them if they know anything about partman's behavior here tomorrow.
[18:35] <Daviey> gwd: Ian Jackson knows not much about debian :)
[18:57]  * koolhead17 wakes up