[12:46] <smoser> maas in ubuntu is still using old import_ephemerals ?
[12:46] <smoser> :-(
[12:47] <smoser> roaksoax, jtv thats correct, right?
[12:48] <smoser> we *really* need to get that fixed, as we want to be delivering updated fast path installer images and the old import_ephemerals does not delete content, meaning guaranteed filesystem full over time.
[12:48] <roaksoax> smoser: yup... they told me it was not ready
[12:50] <smoser> imo that has to land.
[12:52] <smoser> jtv, allenap ? is there a bug that explicitly addresses this? if not I'll open one.
[12:53] <roaksoax> smoser: i dont disagree but if BBBthe tools is not ready we cant uae it
[12:53] <allenap> smoser: jtv will need to answer that one.
[12:53] <roaksoax> smoser: and there are merge proposals already so it is being taken care od
[12:53] <jtv> smoser: I think it falls under the s-cloud-maas-maintainability blueprint.
[12:56] <smoser> it also falls under grave-security-issue if you want me to push that route.
[12:56] <smoser> how far are we from that being functional? i really had thought that this landed. sorry for not raising earlier.
[12:56] <roaksoax> smoser: the tool has landed not the use of it
[12:57] <jtv> What roaksoax said.
[12:57] <roaksoax> jtv: whats the status on the user configurable settibgs?
[12:57] <jtv> What settings specifically?
[12:57] <roaksoax> i raised to rvba that imho disnt seem like a good idea to put everuthibg on pserv.yalm
[12:57] <roaksoax> jtv: maas-import-ephenrals?
[12:57] <jtv> No, we're ditching that.
[12:58] <jtv> Yes, we're talking aboutg maas-import-ephemerals.
[12:58] <roaksoax> jtv: so....?
[12:58] <roaksoax> jtv how will a user select what releases wants to import and so on?
[12:58] <jtv> There's three ways:
[12:58] <jtv> 1. Command-line option.
[12:59] <jtv> 2. yaml config — but we didn't like the way the script rewrote pserv.yaml, so we're moving that to a separate file.
[12:59] <jtv> 3. The existing shell-style config still works.  The script converts it to yaml config.
[12:59] <roaksoax> ok
[13:00] <roaksoax> i guess 2/3 is what i meant
[13:00] <jtv> I guess.
[13:00] <roaksoax> jtv: so if 3 currently works... why add yaml?
[13:00] <roaksoax> jtv: and... what is now preventing its usage?
[13:01] <jtv> The fact that we have changes we want to make to the config.
[13:01] <smoser> roaksoax, consuming shell from python is non ideal. i'd support moving away from that.
[13:01] <jtv> Right now, if you run the script (even with --help!) it writes its new config.  After that it gets harder to move things around the way we intend to.
[13:01] <jtv> What smoser said.
[13:01] <roaksoax> smoser: roght i agree in the meantime it wouldnt hurt would it?
[13:01] <jtv> We've already moved away from that, but we've got some changes we want to make to how we migrate away from it.
[13:02] <roaksoax> jtv: ok
[13:02] <roaksoax> jtv: ETA?
[13:03] <smoser> and how is this planning to be run?
[13:04] <smoser> previously the user could run 'maas-import-ephemerals' and when it returned they knew that the system was ready for use.  while that may not be an ideal interface, it does allow you to actually determine when maas was usable.
[13:04] <smoser> after installation, there needs to be a way to basically block until usable.
[13:04] <jtv> Hoping to be done with the config changes by Wednesday.  But hard to predict, given the state of documentation etc.
[13:05] <jtv> smoser: it's still run in the same way — whether from the CLI or the UI.
[13:06] <smoser> jtv, so in packaged version is this runnable now?
[13:06] <smoser> is that what you're saying ?
[13:07] <jtv> The packaged version still uses the old script.
[13:07] <jtv> But you run it in the same way: CLI or web UI
[13:07] <roaksoax> smoser: the new version is not being installed
[13:22] <smoser> well, i opened bug 1236361.
[13:23] <smoser> i consider this critical to release of 13.10.
[13:25] <jtv> smoser: by the way, I noticed that the old ephemerals script only seems to download the oldest versions of images.
[13:25] <smoser> ?
[13:25] <smoser> i dont think thats the case.
[13:26] <jtv> It was downloading only beta versions of precise & quantal.
[13:26] <smoser> as i'm running it right now against dailies and its dowlnoading saucy 20131007
[13:27] <jtv> Could you check your precise & quantal versions?
[13:27] <smoser> the *new* ehpemerals script was broken (due to server data being broken)
[13:27] <smoser> in that way
[13:27] <smoser> server data is now fixed.
[13:27] <smoser> server data had 'beta' as the "serial" version which C locale sorts to > YYYYMMDD, so simplestremas code was correctly considering those to be the latest
[13:29] <smoser> jtv, i certainly do not want to delay anything, but if you're consuming shell code as 'config' with python, https://gist.github.com/smoser/6466708 does that safely.
[13:34] <jtv> smoser: if you see any specific problem that it would help with, by all means do.
[13:35] <jtv> We do have some advantages that generic code doesn't have though: a statically known set of variables, and an existing relationship between the application and the config file.
[13:37] <smoser> jtv, you dnot actually have a know set of variables.
[13:38] <smoser> you exposed a shell program as a config mechanism.
[13:38] <smoser> which then, users could quite reasonably use however they wanted.
[13:38] <jtv> We have a known set of variables we are interested in.
[13:38] <smoser> but you dont know how they're set.
[13:39] <smoser> (note, you can pass in the list of variables you're interested in to that method, and it will correctly get their values)
[13:40] <smoser> anyway. i'm fine if you dont use it. but it is as close to "correct" a way as I can come up with to solve the "shell was used as config" problem.
[13:40] <jtv> That's nice.  By all means, once you have the tests done, propose a branch that uses this in MAAS!
[14:58] <stokachu> will python-curtin be backported to raring, quantal, and precise?
[15:01] <rbasak> stokachu: AIUI it's destined to go into the cloud-tools pocket of the cloud archive
[15:04] <stokachu> rbasak: ok thanks
[15:12] <smoser> stokachu, no.
[15:13] <smoser> not necessary
[15:13] <stokachu> so funny story if you run make install-dependencies in the maas code tree it removes all network-manager related packages
[15:13] <stokachu> leaving you without internet
[15:13] <smoser> good times.
[15:13] <smoser> you didn't need that interweb stuff anyway
[15:13] <stokachu> lol
[15:15] <smoser> stokachu, you dont need to port python-curtin to raring/quantal or precise.
[15:15] <smoser> because pytho-curtin is installed on the maas server
[15:16] <smoser> it is packed up into a self extracting tarball, and shoved across to the installing node.
[15:16] <smoser> and then invoked over there.
[15:16] <stokachu> in the control file it depends on python-curtin
[15:16] <smoser> thats right.
[15:16] <smoser> maas does depend on that.
[15:17] <smoser> you will not get maas with curtin support on Q or R.
[15:17] <smoser> you get it on P through cloud-archive tools
[15:17] <stokachu> so are all maas developers running saucy at this point?
[15:17] <stokachu> or will buildout handle getting a maas development instance up locally
[15:18] <smoser> oh. i see.
[15:18] <smoser> i dont know the answer to that question.
[15:18] <stokachu> i tried following the hacking.txt file but it left me without network connectivity
[15:20] <smoser> stokachu, my response to any software package that says "hey, run this as root" is "run this in a lxc container or new cloud instance".
[15:21] <smoser> which makes running saucy or precise easy, and alleviates the network manager hardship.
[15:21] <smoser> i'm not saying thats a good thing, but its a general purpose solution to the problem.
[15:21] <stokachu> ok
[15:51] <smoser> roaksoax, https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1236433
[15:55] <roaksoax> smoser: did you only upgrade maas or rabbitmq or something else too?
[15:55] <roaksoax> smoser: you are also upgrading upstart: upstart:amd64 (1.10-0ubuntu3, 1.10-0ubuntu6)
[15:55] <roaksoax> smoser: might be related?
[15:56] <smoser> see bug.
[15:56] <smoser> roaksoax, fwiw, it still seems unable to power on nodes for me :-(
[15:57] <smoser> (even after starting the daemon)
[15:58] <roaksoax> smoser: weird, I have been running a server myself without issues
[15:58] <roaksoax> smoser: i'll check in a bit
[16:17] <stokachu> so user provided preseed files are only available for enlist and commissioning? is there a way to override generic preseed during install?
[16:19] <roaksoax> stokachu: you can modify the preseed as you wish
[16:20] <stokachu> roaksoax: directly modifying the generic preseed or through a user supplied preseed?
[16:20] <roaksoax> stokachu: directly modifying the preseed. you can create your own preseeds there and they will be added to the path, and you will have to add what you want to be added to the generic preseed from those user supplied ones
[16:21] <roaksoax> stokachu: for example, preseed_master imports from generic, so you could techniclally create another preseed similar to generic, and in preseed_master you would need to "call" what's in your preseed
[16:23] <stokachu> so generic inherits preseed_master so wouldnt i need to create a generic_custom?
[16:23] <stokachu> or is this the problem with Tempita
[16:24] <stokachu> the documentation states Tempita's inheritence is 'weird'
[16:27] <strikov> hey guys. i just switched my toy maas server from 12.04 to 13.04 and met very strange issue. when i accept the node (either using dashboard or maas-cli) system doesn't create anything in pxelinux.cfg (in fact this folder is not created) and my nodes can't start commissioning. any ideas on how to fix that? thanks
[16:27] <stokachu> so if i wanted to reconfigure the network on the node during installation do i edit generic or preseed_master
[16:29] <stokachu> so creating amd64_generic_saucy will override generic, but i would still need to modify preseed_master to accept new network defintions, is that correct?
[16:31] <stokachu> roaksoax: ah i see now what you meant by calling whats in my preseed
[16:32] <roaksoax> stokachu: :)
[16:33] <stokachu> roaksoax: so in the web ui when a preseed is created for a node it'll pick up amd64_generic_precise if the commissioning is set to that os image?
[16:33] <stokachu> os image being precise
[16:38] <roaksoax> stokachu: huh?
[16:40] <stokachu> roaksoax: when commissioning a node will it pickup amd64_generic_precise if it exists?
[16:42] <strikov> well, i figured out that maas from 13.04 uses python/twisted-based tftp server instead of original tftpd. it mean that it can handle requests w/o pxelinux.cfg folder. but my nodes are stopped trying to pull pxelinux.cfg/<mac> which means that this tftp server doesn't work well.
[16:44] <roaksoax> stokachu: you added a preseed from the webui?
[16:44] <roaksoax> stokachu: for commissioning/enlistment you can only add scripts that will do different taskls, not preseeds
[16:45] <stokachu> roaksoax: where does the installer pick up amd64_generic_precise from if it exists?
[16:45] <stokachu> preseed_master hardcodes the network, i need to override that
[16:45] <roaksoax> stokachu: what's amd64_generic_precise?
[16:46] <stokachu> roaksoax: that is my user-provided preseed
[16:46] <stokachu> from the doc: As you can see this mechanism is also used to calculate the base preseeds for
[16:46] <stokachu> all of installation, enlistment and commissioning.  It allows end users to
[16:46] <stokachu> add, for example, a file named ``amd64_generic_saucy`` that would be used
[16:46] <stokachu> instead of the ``generic`` template at installation time.
[16:47] <roaksoax> stokachu: idk how will affect curint installation method which uses the style of enlistment/commissioning, but if you are using d-i
[16:47] <roaksoax> commissioning/enlistment are completely different from installation preseeds
[16:47] <stokachu> roaksoax: that i understand, i am more concerned with how to override the preseed during installation
[16:48] <roaksoax> stokachu: ok, so have you added your preseed to /etc/maas/preseeds?
[16:48] <stokachu> before the actuall install procedure
[16:48] <roaksoax> stokachu: and defined a section
[16:48] <roaksoax> and called it in preseed_master?
[16:48] <stokachu> so thats my question do i create a amd64_generic_precise and inherit preseed_master
[16:49] <roaksoax> stokachu: if you'd show me a diff of what you are trying to do maybe I could understand better :)
[16:49] <stokachu> ok one sec
[16:51] <stokachu> roaksoax: http://paste.ubuntu.com/6205699/
[16:52] <stokachu> preseed_master call self.network_conf, but that only exists in amd64_generic_precise
[16:52] <stokachu> is this the correct way to override the installation for a amd64 precise install via maas?
[16:52] <roaksoax> stokachu: yeah that should work, but if network_conf is only for mad64
[16:53] <roaksoax> then you would need to do stuff like: {{if node.architecture in {'i386/generic', 'amd64/generic'} }}
[16:53] <stokachu> put that in the preseed_master right?
[16:54] <roaksoax> stokachu: http://pastebin.ubuntu.com/6205703/
[16:54] <stokachu> ah ok
[16:55] <stokachu> roaksoax: thanks this clears up some stuff for me to work on
[16:56] <stokachu> roaksoax: because i named it amd64_generic_precise this will only be read during a precise install correct?
[16:56] <stokachu> everything else uses generic
[16:59] <roaksoax> stokachu: i don't know if the naming convention works that way
[16:59] <roaksoax> stokachu: better ask Ruetobas
[16:59] <roaksoax> err
[16:59] <roaksoax> rvba:
[16:59] <roaksoax> sorry
[16:59] <roaksoax> :)
[17:00] <stokachu> roaksoax: im referencing the preseeds.rst documentation
[17:00] <roaksoax> stokachu: I have not tested that, but if that what the documentation says then I would give it a try
[17:00] <stokachu> there also doesn't seem to be a way to just create a install preseed for a series without defining the architecture
[17:01] <stokachu> ok ill do some more testing on this
[17:17] <smoser> strikov, i think likely the tftp server is not listening on the right interface
[17:22] <strikov> smoser: i had pretty the same thought first, but my node can pull pxelinux.0 w/o any problems
[17:22] <strikov> smose: i assume it pulls this file through tftp as well
[17:24] <smoser> strikov, its od..
[17:24] <smoser> i've seen this before.
[17:24] <smoser> is your node virtual ?
[17:24] <strikov> yes, the whole environment is vbox based
[17:24] <smoser> https://bugs.launchpad.net/maas/+bug/1051626
[17:25] <strikov> smoser: interesting, but it looks like guys in the bug can't pull pxelinux.0 as well
[17:26] <strikov> smoser: we may observe different sides of the same issue though
[17:26] <smoser> strikov, no. se my coments in line 13.
[17:26] <smoser> comment 13
[17:26] <smoser> and even 7.
[17:27] <strikov> ah, i see
[17:27] <strikov> maas from 12.04 worked fine for me in the same environment
[17:28] <strikov> i need to check if pxe binary changed a lot
[17:28] <smoser> strikov, its not the pxe binary
[17:28] <smoser> see my other comments there. . i basically tested everything hardy -> 12.04
[17:31] <strikov> aha, well it looks like the issue began when maas switched to its own tftp server, right?
[17:31] <strikov> because 12.04 was the last maas with original tftp
[17:32] <strikov> did you try gavin's solution with restarting pserv?
[17:35] <smoser> strikov, i have tried many things. and i'm not sure if i hit this or not any more.
[17:35] <strikov> okay, i'll give it a try now. thanks for pointing to the bug.
[17:35] <smoser> strikov, could you try adding 'next-server' entry in /etc/maas/dhcpd.conf
[17:35] <smoser> and setting it correctly
[17:35] <smoser> i'm just curious.
[17:36] <strikov> okay, my virtual machine is reinstalling now, i'll check when it is ready
[18:14] <strikov> smoser: restaring pserv doesn't help
[18:15] <strikov> smoser: what did you mean by next-serv, do you want me to put my original server ip there or to setup external tftpd and put it there?
[18:17] <smoser> add an entry in /etc/maas/dhcpd.conf for 'next-server YOUR.SERVER.IP.HERE'
[18:17] <smoser> right underneith the 'filename' entry
[18:19] <strikov> smoser: i see and actually i found tons of errors in /var/log/maas/pserv.log while doing pxe boot
[18:19] <strikov> smoser: it can't find some images, trying to understand what's happening
[18:22] <strikov> smoser: actually it can't find i386 images because i disabled pulling them
[18:23] <smoser> strikov, yeah... so that sucks.
[18:23] <smoser> i think this is basically  unavoidable.
[18:23] <strikov> smoser, next-server doesn't help
[18:23] <smoser> that you have to have the i386
[18:23] <smoser> for enlistment at least
[18:24] <smoser> as maas doesn't know the arch at tha tpoint.
[18:24] <strikov> i did enlistment
[18:24] <strikov> with the bootable cd
[18:24] <strikov> at this point maas should know my arch i think
[18:26] <strikov> smoser: eod for me. i'll keep trying tomorrow and let you know if i find the solution
[18:26] <strikov> smoser: thanks for helping, ttyl
[18:28] <smoser> strikov, i agree, it shoudl know
[18:51] <smoser> roaksoax,
 smoser, [Mon Oct 07 18:50:06 2013] [crit] [client 127.0.0.1] configuration error:  couldn't perform authentication. AuthType not set!: /MAAS/static/images/amd64/generic/precise/xinstall/root.tar.gz   <- any hint?
[18:59] <roaksoax> smoser: that's apache?
[19:01] <adam_g> dropping 'Require all granted' from maas-cluster-http.conf helps
[19:01] <adam_g> roaksoax, yea
[19:03] <adam_g> smoser, curtin worked fine otherwise \o/
[19:04] <roaksoax> adam_g: weird, before that required all granted was needed otherwise it wouldn't work
[19:04] <roaksoax> adam_g: hold done, is this precise?
[19:05] <roaksoax> adam_g: is this precise?
[19:05] <adam_g> roaksoax, it is 1.4+bzr1656+dfsg-0ubuntu2~ctools0  on precise
[19:05] <roaksoax> adam_g: that's the problem them, for saucy the http ocnfig is different
[19:05] <roaksoax> which is why it fails in precise
[19:05] <roaksoax> due to different apache
[19:06] <adam_g> oh hum
[19:06] <adam_g> that stinks
[19:06] <smoser> gah.
[19:06] <smoser> that does stink.
[19:06] <roaksoax> smoser: i guess we could try fix that in postinst
[19:06] <smoser> well, you probably shouldnt edit a conffile postinst
[19:07] <smoser> though, right?
[19:07] <roaksoax> smoser: yeah but that is a config file being shipped by maas btw
[19:07] <smoser> right.
[19:07] <smoser> bugger
[19:08] <roaksoax> yup
[19:08] <adam_g> some good pointers in https://wiki.debian.org/Apache/PackagingFor24 for supporting both apaches
[19:09] <roaksoax> ok i think i know how to fix it
[19:10] <smoser> oh nice.
[19:10] <smoser> IfVersion
[19:10] <roaksoax> yup
[19:11] <smoser> roaksoax, i'll file a bug
[19:11] <roaksoax> smoser: ok
[19:17] <smoser> roaksoax, https://bugs.launchpad.net/cloud-archive/+bug/1236544
[19:19] <roaksoax> smoser: thank you
[19:22] <sconklin> I'm unable to bootstrap the juju environment on my raring maas server. Best I can tell from searching, it's because all my nodes are "allocated to root", and not "ready". How can I return them to ready status
[19:24] <smoser> sconklin, maas-cli $MAASNAME node release "$nodeid"
[19:25] <roaksoax> smoser: makes sense? http://paste.ubuntu.com/6206324/
[19:25] <roaksoax> adam_g: could you pelase test: http://paste.ubuntu.com/6206324/
[19:26] <sconklin> smoser: what is $MAASNAME?
[19:26] <smoser> sconklin, however you use maas-cli
[19:27] <smoser> if you've not used maas-cli you need to set that up.
[19:27] <sconklin> never used it
[19:28] <smoser> http://paste.ubuntu.com/6206336/
[19:29] <smoser> you can do the same stuff in the web ui, click 'release' for each of the nodes.
[19:29] <sconklin> I don't see 'release' in the UI
[19:29] <smoser> or 'stop node' i guess.
[19:29] <sconklin> or stop node
[19:30] <smoser> for the node?
[19:30] <smoser> you have to go to the node' spage.
[19:32] <roaksoax> smoser: proposed fix... just need someone to test it: https://code.launchpad.net/~andreserl/maas/lp1236544/+merge/189692
[19:32] <adam_g> roaksoax, works but two things: should be closed with </IfVersion>, not </If> and you need to enable the 'version' module for that tag to work
[19:33] <smoser> adam_g, you have a funny definiton of "works"
[19:36] <stokachu> doing a clean upgrade from maas 1.2 to maas 1.4 in cloud-tools shows this error http://paste.ubuntu.com/6206361/
[19:36] <stokachu> any way around that other than removing and installing maas 1.4?
[19:44] <stokachu> hmm i did a clean install of maas and get that same error during the migration
[19:47] <smoser> wow.
[19:47] <smoser> stokachu, please file a bug.
[19:48] <guntbert> did anybody see my report about http://maas.ubuntu.com/docs/install.html ?
[19:48] <smoser> adam_g, did you test roaksoax config change at https://code.launchpad.net/~andreserl/maas/lp1236544/+merge/189692
[19:49] <AskUbuntu> Can MAAS install non-ubuntu operating system | http://askubuntu.com/q/354996
[19:50] <adam_g> smoser, i tested the equiv manually, but only works when the version module is enabled. there's a corresponding packaging change that needs to happen
[19:51] <stokachu> smoser: figured it out, maas build depends on python-django and doesn't set a min version requirement as maas 1.4 needs at least django 1.4
[19:51] <stokachu> ill file a bug with a patch
[19:51] <smoser> roaksoax, ^
[19:52] <roaksoax> adam_g: yeah typo :)
[19:52] <stokachu> or i can just do a MP
[19:52] <roaksoax> adam_g: is the module called 'version'? (a2enmode version)
[19:52] <adam_g> roaksoax, yeah
[19:52] <smoser> stokachu, we need a bug.
[19:52] <roaksoax> adam_g: k thanks
[19:52] <smoser> then you can do a MP
[19:53] <roaksoax> smoser: i think we can drop the build-dep in python-django
[19:53] <smoser> but we have to have a bug at this point in the ubuntu cycle
[19:53] <smoser> roaksoax, id ont follow. stokachu is explicitly stating we need runtime depends (i think)
[19:53] <stokachu> smoser: ok ill create it too
[19:53] <stokachu> bug that is
[19:54] <roaksoax> 15:54 < stokachu> smoser: figured it out, maas build depends on python-django and doesn't set a min version requirement as maas 1.4 needs at least django 1.4
[19:54] <stokachu> GenericIPAddressField was introduced in django 1.4
[19:54] <smoser> roaksoax, yeah, how would we drop the build-dep ? i'm confused.
[19:55] <roaksoax> smoser: we don't really build anything (binaries and such)
[19:55] <smoser> you could remove a 'Build-Depends' possibly, but who cares. the problem is that we are missing a 'Depends'
[19:56] <smoser> well, roaksoax generally speaking i think the "best practice" is to build-depends on everything you Depends on and run 'make test' and use dh-python magic to determine your runtime depends wherever you can.
[19:56] <roaksoax> smoser: we are missing versioning, not a depends
[19:56] <smoser> right.
[19:56] <smoser> so how would dropping a build-depends change anything.
[19:57] <roaksoax> smoser: http://paste.ubuntu.com/6206456/
[19:57] <roaksoax> makes sense?
[19:57] <stokachu> roaksoax: yea that works
[19:59] <smoser> roaksoax, is it 'maas-region-controller' that depends on it? or is it python-django-maas.
[19:59] <smoser> i suspect the first, but just checking.
[19:59] <roaksoax> smoser: the first one
[19:59] <smoser> k. then that change sems to make sense to me.
[20:04] <roaksoax> smoser: https://code.launchpad.net/~andreserl/maas/packaging_lp1236544/+merge/189694
[20:04] <roaksoax> https://code.launchpad.net/~andreserl/maas/lp1236544/+merge/189692
[20:04] <roaksoax> all yours
[20:05] <smoser> roaksoax, you need the packaging change alos
[20:05] <smoser> right?
[20:05] <smoser> to enable the config mod
[20:05] <roaksoax> smoser: i did that already, check both MP's
[20:05] <smoser> oh i see.
[20:05] <smoser> :)
[20:05] <smoser> sorry
[20:05] <roaksoax> :)
[20:05] <roaksoax> no worries
[20:05] <smoser> but you need sconklin's bug number for your debian/control change
[20:05] <smoser> release team will want the bug number
[20:06] <sconklin> smoser: ??
[20:06] <smoser> oh. sorry.
[20:06] <roaksoax> stokachu: what's the bug number
[20:06] <smoser> stokachu's bug
[20:06] <roaksoax> adam_g: what did you install to get the version module:
[20:06] <roaksoax> roaksoax@pursue:/etc/openvpn$ sudo a2enmod version
[20:06] <roaksoax> ERROR: Module version does not exist!
[20:06] <stokachu> i need to create the bug
[20:07] <stokachu> lemme do that right now
[20:09] <stokachu> roaksoax: 1236572
[20:10] <roaksoax> stokachu: thank you sir!
[20:10] <stokachu> roaksoax: np :D
[20:11] <guntbert> guys I can understand that you don't want to deal with apparent errors in the documentaion - in the meantime I filed a bug report - but it would have been nice if someone had said so :-)
[20:12] <stokachu> guntbert: did you associate an MP with it?
[20:13] <guntbert> stokachu: MP?
[20:13] <stokachu> guntbert: a merge proposal with the documentation changes
[20:13] <smoser> guntbert, i personally don't agree with bigjools' statement there.
[20:13] <roaksoax> stokachu: yep
[20:14] <adam_g> roaksoax, i didn't install anything to have that module available
[20:15] <roaksoax> adam_g: weird... I don't seem to have it
[20:16] <guntbert> no, I didn't have any proposal yet, atm I am just trying to follow some guide and stumbled over that discrepancy - anyway the bug I filed is #1236571
[20:17] <stokachu> guntbert: cliking import boot images really just shells out to maas-import-pxe-files
[20:18] <stokachu> afaics
[20:19] <guntbert> stokachu: I see, so the instructions still apply - and it was only a misunderstanding
[20:19] <stokachu> guntbert: i think you have a valid bug
[20:19] <stokachu> guntbert: just needs some better wording on the docs is all
[20:20] <roaksoax> adam_g: ok that module seems to be available in precise but not in suacy
[20:20] <roaksoax> smoser: ^^
[20:21] <guntbert> stokachu: well there are always the same problems with docs for a fast moving project :-)
[20:21] <stokachu> guntbert: agreed -- i recently fixed a few just a few days ago
[20:21] <smoser> roaksoax, really?
[20:21] <roaksoax> y
[20:21] <smoser> what is the module name ?
[20:21] <roaksoax> smoser: version
[20:21] <roaksoax> smoser: you give it a try to see im not crazy
[20:22] <smoser> package ?
[20:22] <roaksoax>  the package has to a2enmod version if 2.2 is installed. For 2.4, we will compile mod_version in statically.
[20:23] <guntbert> have a nice time - bed time here :-)
[20:29] <smoser> roaksoax, so you ahve a fix?
[20:29] <smoser> who is "we" ?
[20:29] <smoser> i'm confused
[20:31] <roaksoax> smoser: i read that somewhere
[20:32] <roaksoax> smoser: i don't have a fix yet
[20:32] <roaksoax> smoser: we should probably be carrying a delta otherwise
[20:32] <roaksoax> smoser: https://wiki.debian.org/Apache2Transition#Should_we_support_a_transitional_fallback_configuration_which_allows_web_apps_to_work_with_both_2.2_and_2.4_packages
[20:33] <adam_g> roaksoax, you should only need to 'a2enmod version' from postinst if running apache2.2
[20:34] <adam_g> https://wiki.debian.org/Apache/PackagingFor24 has a good example for detecing that from postinst
[20:38] <roaksoax> adam_g: ok so this should be it: http://paste.ubuntu.com/6206625/
[20:38] <roaksoax> smoser: http://paste.ubuntu.com/6206625/
[20:41] <adam_g> roaksoax, looks reasonable
[20:42] <roaksoax> smoser: https://code.launchpad.net/~andreserl/maas/packaging_lp1236544/+merge/189694
[20:43] <roaksoax> adam_g: ty
[20:45] <smoser> roaksoax, alternatively you just dont care if the a2enmod fails
[20:45] <smoser> right?
[20:47] <roaksoax> smoser: better? http://paste.ubuntu.com/6206668/
[20:47] <smoser> well, thats not really waht i was saying.
[20:47] <smoser> yours is fin ei thikn
[20:48] <smoser> i was saying you can just only 'a2enmod version || true'
[20:48] <smoser> on apache2 it runs fine.
[20:48] <smoser> errr on 2.2 tha tworks
[20:48] <smoser> on 2.4 it will fail, but you dont care
[20:53] <roaksoax> smoser: right
[20:53] <roaksoax> smoser: either way works i guess
[20:57] <roaksoax> smoser: do you want me to change it?
[20:59] <smoser> yours is fine. i think.
[20:59] <smoser> if you've tested it.
[21:06] <roaksoax> smoser: i haven't
[21:07] <smoser> alright. i have to run for a couple hours. ill be in later.
[21:09] <roaksoax> smoser: k enjoy!
[21:09] <smoser> roaksoax, thanks for your work on this.
[21:09] <roaksoax> smoser: np
[22:43] <roaksoax> smoser: i think maas-signal or maas are broken :/
[22:43] <bigjools> o/ roaksoax
[22:43] <roaksoax> bigjools: howdy
[22:44] <roaksoax> bigjools: back from holidays?
[22:44] <bigjools> yes, 15m ago
[22:44] <roaksoax> bigjools: hope you enjoyed it !
[22:44] <bigjools> ETOOMUCHEMAIL
[22:44] <bigjools> I did, thanks!
[22:44] <bigjools> might not do so much driving next time
[22:45] <roaksoax> bigjools: heh! the fun of driving
[22:46] <roaksoax> bigjools: so now that you are here.. you can help me debug this
[22:46] <roaksoax> bigjools: :P
[22:46] <bigjools> roaksoax: normally it's fine but not so much with 4 kids
[22:46] <bigjools> roaksoax: I can try but I am considering turning off IRC so I can catch up with email
[22:46] <bigjools> so just to warn you :)
[22:47] <roaksoax> bigjools: haha i think that might be a bad idea.. FinalFreeze on Thrusday :)
[22:47] <bigjools> I know ...
[22:47] <bigjools> I need to write release notes
[22:47] <roaksoax> bigjools: ok so just quickly. I'm enabling moonshot to hopefully land it in saucy
[22:47] <bigjools> cool
[22:48] <roaksoax> bigjools: so the issue seems that maas doesn't seem to be updating the power params in maas
[22:48] <roaksoax> bigjools: on commissioning
[22:48] <roaksoax> bigjools: the power_type gets set, but not power_user,power_pass,power_address
[22:48] <roaksoax> bigjools: where can I debug this?
[22:49] <bigjools> roaksoax: turn on http debugging using the API call to change settings
[22:49] <roaksoax> bigjools: (if i change power tyupe of ipmi the same result, so I know this is not only a moonshot thing)
[22:49] <bigjools> and you can see the message that maas-signal sends
[22:50] <bigjools> if you're not familiar with it I can tell you how
[22:50] <roaksoax> bigjools: yeah i just need to know how to enable the logging fro apache2
[22:51] <roaksoax> (http debugging)
[22:51] <bigjools> oh it's changed in my absence....
[22:52] <bigjools> roaksoax: it dumps at log level DEBUG
[22:52] <bigjools> you might be able to change that in the web UI
[22:52] <bigjools> but I don't know offhand how to set it in the API
[22:53] <stokachu> what log file contains information about what happens after i press 'start node'
[22:53] <stokachu> ive setup ssh keys and have virsh configured over ssh for the power type
[22:53] <roaksoax> bigjools: uhmmm
[22:53] <roaksoax> bigjools: can't we do this in apache2?
[22:53] <bigjools> no
[22:54] <bigjools> it's better to do it in Django
[22:54] <bigjools> you get a nice formatted dump
[22:54] <bigjools> just hack the log level at the end of src/maasserver/middleware.py
[22:54] <bigjools> and restart apache
[22:54] <bigjools> we're supposed to be able to set this on the fly but I don't know how now that someone changed this code
[22:54] <roaksoax> bigjools: /etc/maas/maas_local_settings.py has the logging
[22:54] <roaksoax> bigjools: so is this for handlers or loggers or what?
[22:55] <roaksoax> adh dah
[22:55] <roaksoax> handlers
[22:55] <bigjools> all http comms are logged at DEBUG by default
[22:55] <bigjools> so turn on DEBUG
[22:57] <roaksoax> no luck doing it in the config
[22:58] <roaksoax> bigjools: so this would output to maas.log right?
[22:59] <bigjools> roaksoax: yes
[22:59] <bigjools> did you restart apache after changing the config?
[22:59] <roaksoax> bigjools: yup
[23:04] <roaksoax> bigjools: no nothing
[23:04] <roaksoax> i even restart the machine
[23:04] <bigjools> roaksoax: just hack the log level in that source so it's at INFO
[23:04] <bigjools> then restart apache
[23:05] <bigjools> you'll see stuff in either apache's log or maas.log, can't remember which
[23:05] <roaksoax> bigjools: logger.debug("%s\n%r\n%s", header, request, request.content)
[23:05] <roaksoax> i changed that from logger.info to logger.debug
[23:05] <bigjools>     log_level = logging.DEBUG
[23:06] <roaksoax> bigjools: i can't find that in maasserver/middleware.py
[23:06] <bigjools> you have an old source
[23:06] <bigjools> trunk is newer
[23:06] <roaksoax> bigjools: this is trunk from last week
[23:06] <roaksoax> -_-'
[23:07] <roaksoax> anyway,. gonna get a newer maas then
[23:07] <bigjools> this change is in r1660
[23:08] <roaksoax> bigjools: i have 1655 or so
[23:08] <roaksoax> :)
[23:08] <bigjools> the old code is changable with an API call then
[23:08] <roaksoax> bigjools: what's the api call? :)
[23:09] <bigjools> roaksoax: set "request_log_debug" in settings
[23:13] <roaksoax> bigjools: that crashes the UI
[23:13] <bigjools> sigh
[23:13] <bigjools> probably why the code got changed :)
[23:22] <roaksoax> probably
[23:22] <roaksoax> ok i'll let this build and re-test
[23:22] <roaksoax> bigjools: because if this is really a bug
[23:22] <roaksoax> then is critical
[23:22] <bigjools> sure
[23:55] <roaksoax> bigjools: ok im in newer trunk
[23:55] <bigjools> roaksoax: ok so look for "log_level = logging.DEBUG" near the bottom of middleware.py
[23:55] <roaksoax> bigjools: changed from debug to info
[23:55] <bigjools> and s/DEBUG/INFO/ then restart apache
[23:56] <roaksoax> and don't really see any log
[23:56] <bigjools> something must be logged somewhere
[23:56] <bigjools> do some UI or API requests
[23:57] <roaksoax> bigjools: i just see the normal stuff
[23:57] <bigjools> :/
[23:57] <bigjools> I know this stuff works, I've seen it
[23:57] <bigjools> as I said, not sure which log though
[23:57] <roaksoax> bigjools: i'm tailing apache logs, all of maas' logs
[23:57] <roaksoax> etc
[23:59] <roaksoax> bigjools: this is the only thing i see: ==> /var/log/apache2/access.log <==
[23:59] <roaksoax> 10.18.1.40 - - [07/Oct/2013:18:58:51 -0500] "POST /MAAS/metadata//2012-03-01/ HTTP/1.1" 200 181 "-" "Python-urllib/2.7"
[23:59] <bigjools> roaksoax: ah bugger,  this logging only works for maasserver, there's a different api for metadata
[23:59] <roaksoax> plop
[23:59] <roaksoax> bigjools: how can we see that then :)