[11:00] <ehg> anyone else come across go juju's upgrade-charm failing after 9 upgrades of a charm?
[11:01] <ehg> maybe due to: /worker/uniter/charm/deployer.go:prefix = prefix + time.Now().Format("-%Y%m%d-%H%M%S")
[11:01] <ehg> not formatting the date properly, and coming out as a string
[11:01] <ehg> literally
[11:26] <ehg> it causes a pretty nasty infinite loop that runs config-changed :(
[11:27] <ehg> colleague has filed a bug here: https://bugs.launchpad.net/juju-core/+bug/1197369
[11:27] <_mup_> Bug #1197369: more than 10 upgrades to a charm causes horrible infinite loop <juju-core:New> <https://launchpad.net/bugs/1197369>
[11:27] <ubot5`> Launchpad bug 1197369 in juju-core "more than 10 upgrades to a charm causes horrible infinite loop" [Undecided,New]
[11:27] <_mup_> Bug #1197369: more than 10 upgrades to a charm causes horrible infinite loop <juju-core:New> <https://launchpad.net/bugs/1197369>
[11:27] <ehg> snap
[11:59] <stub> ehg: I suspect it is fixed in the dev version. I think I've seen it, but not since switching to the PPA version
[13:00] <ehg> stub: it seems to be in head still, http://bazaar.launchpad.net/~go-bot/juju-core/trunk/view/head:/worker/uniter/charm/deployer.go#L191
[13:00] <ehg> i'm not too familiar with bzr, however
[16:02] <arosales> juju charm meeting starting in a few minues
[16:02] <arosales> *minutes
[16:02] <arosales> on air URL: http://youtu.be/ZQ47UzK65-Q
[16:03] <arosales> etherpad: http://youtu.be/ZQ47UzK65-Q
[16:04] <arosales> sorry
[16:04] <arosales> etherpad: https://plus.google.com/hangouts/_/cb8d75f1182f29cddb2b46a565cb9ff361af9e09?authuser=0&hl=en
[16:04] <arosales> that is actually the hangout URL if folks want to join
[16:05] <arosales> real etherpad link: http://pad.ubuntu.com/7mf2jvKXNa
[16:05] <arosales> :-)
[16:07] <arosales> marcoceppi, will be checking to see if he can update the onair
[16:08] <arosales> http://ubuntuonair.com/ also updated
[16:09] <smartboyhw> arosales, um, since jcastro is on holiday, I need to ask you: The JuJu championships, 13-18-year-olds are supposed to contact you guys.
[16:10] <smartboyhw> So, how to contact? jcastro told me to send an  email to him but he's on holiday, not probably the best idea...
[16:10] <smartboyhw> Or is he back!!?!??!
[16:10] <smartboyhw> jcastro, ping ping ping
[16:12] <arosales> smartboyhw, hello
[16:13] <smartboyhw> arosales, hey:)
[16:13] <jcastro> hey guys
[16:13] <jcastro> yeah, smartboyhw I have your info
[16:13] <smartboyhw> jcastro, yay:)
[16:16] <arosales> ah jcastro !
[16:16] <jcastro> I've sent you an email
[16:17] <smartboyhw> Wait, my parents submit MY entry!?!?!?!?
[16:17] <smartboyhw> What kind of rule is that?
[16:17]  * smartboyhw :O
[16:18] <jcastro> you're underage, there's a bunch of legal stuff we have to do
[16:18] <smartboyhw> I mean, it's OK to let them have the prize money... But I think I should be the one who submits the entry myself, jcastro.
[16:19] <jcastro> I don't really make these rules
[16:19]  * smartboyhw decides not to take part due to this strange rule.
[16:20] <smartboyhw> If I don't have control over what I enter, what's the point?
[18:13] <CyberJacob> Hi
[18:14] <CyberJacob> Anybody here?
[18:23] <marcoceppi> CyberJacob: Hi!
[18:23]  * CyberJacob is now reinstalling to try and fix the problem
[19:08] <CyberJacob> ok, so now I have my first problem again
[19:08] <CyberJacob> and I don't know how I fixed it
[19:40] <arosales> CyberJacob, what is the issue you are seeing?
[19:40] <arosales> CyberJacob, http://pastebin.ubuntu.com
[19:50] <CyberJacob> arosales: http://pastebin.ubuntu.com/5841424/
[19:50] <CyberJacob> arosales: everything gets stuck on pending
[19:50]  * arosales taking a look
[19:51] <arosales> CyberJacob, ah so this is a maas provider
[19:51] <CyberJacob> yup
[19:51] <arosales> CyberJacob, what version of juju are you running?
[19:52] <CyberJacob> 0.7
[19:52] <CyberJacob> fresh from apt-get
[19:52] <arosales> cool
[19:52] <CyberJacob> on a brand new MAAS install
[19:54] <arosales> CyberJacob, and to confirm your environment did you grab maas from the ppa or ubuntu archive?
[19:55] <CyberJacob> I grabbed a server install ISO and selected "multiple server install with MAAS" from it's grub
[19:55] <arosales> 12.04 server install?
[19:55] <CyberJacob> 13.04
[19:55] <arosales> ok
[19:57] <arosales> CyberJacob, I take it all follow on deploy after the bootstarp go into pending
[19:57] <CyberJacob> yup
[19:58] <hazmat> arosales, could you pastebin a tail -n 200 of  /var/log/maas/maas.log
[19:58] <CyberJacob> and juju bootstrap went fine
[19:59] <hazmat> CyberJacob, on the maas server
[19:59] <arosales> CyberJacob, your set of enlistments looks good too from the maas side?
[19:59] <CyberJacob> I think so
[19:59] <CyberJacob> how do I check?
[20:00] <hazmat> CyberJacob, a pastebin of /var/log/maas/maas.log would help figure out the issue
[20:01] <hazmat> CyberJacob, another useful log here would be /var/log/juju/provisioning-agent.log on the juju bootstrap server
[20:01] <CyberJacob> hazmat: http://pastebin.ubuntu.com/5841462
[20:01] <hazmat> hmm
[20:02] <CyberJacob> from what I can tell, Node2 is the juju master
[20:02] <CyberJacob> (it booted up when I ran bootstrap)
[20:03] <CyberJacob> hazmat: http://pastebin.ubuntu.com/5841464/
[20:04] <hazmat> CyberJacob, thanks
[20:06] <hazmat> CyberJacob, this should already be fixed in 0.7.. but it looks alot like a port specification bug in the maas provider.. in your juju provider config for maas can you add  :80 to the maas node address portion of the url
[20:06] <hazmat> ie maas-server: my-maas-node:80
[20:07] <hazmat> err i mean... maas-server: http://my-maas-node:80
[20:07] <roaksoax> hazmat: here!
[20:07] <hazmat> CyberJacob, ^
[20:07] <hazmat> roaksoax, what do you make of this maas.log output.. http://pastebin.ubuntu.com/5841462
[20:07] <CyberJacob> would that be on the server I ran `juju bootstrap` from?
[20:08] <hazmat> CyberJacob, yes it goes into the juju client 's environment.yaml
[20:08] <CyberJacob> ok, done
[20:08] <roaksoax> in which step is this happening?
[20:08] <CyberJacob> do I need to restart the service?
[20:08] <hazmat> CyberJacob, you have to execute a command that will modify the environment for it to sync to the bootstrap node
[20:09] <hazmat> CyberJacob, ie.. add-unit / deploy/destroy-service etc
[20:09] <roaksoax> first seems that an invalid MAC address is being sent to maas, then no mac address being sent, then mac address duplication
[20:10] <CyberJacob> hazmat: ok, just tried to deploy another charm
[20:11] <CyberJacob> now I have two machines with instance-id pending
[20:12] <arosales> roaksoax, note this is a 13.04 server media install of maas
[20:14] <roaksoax> arosales: the issues doesn't really seem to be MAAS related, but rather whomever is interacting with MAAS.
[20:14] <roaksoax> that's why I need to know when is this happening
[20:15] <arosales> roaksoax, gotcha
[20:15] <hazmat> CyberJacob, could you pastebin any new output from the provisioning agent log
[20:16] <roaksoax> arosales: btw.. do we have a juju-core documentation to use with lxc?
[20:16] <arosales> roaksoax, so aiui the issue at hand is deploying services after the initial juju bootstrap go into pending
[20:17] <CyberJacob> hazmat: http://pastebin.ubuntu.com/5841486/
[20:17] <arosales> roaksoax, juju-core hasn't landed local provider yet
[20:18] <arosales> roaksoax, also for my maas debugging education there is "check-commissioning" helpful to verify nodes are "ready" for deployment onto, or is there a better method?
[20:19] <hazmat> hmm.. looks like maas isn't listening on the port from that provisioning agent log
[20:19] <CyberJacob> hazmat: is there a way to force it to sync to the bootstrap node without deploying something?
[20:20] <roaksoax> arosales: the issue above seems to be related to enlistment. As far as commissioning, the only way to see what's going on with the commissioning process, would be to get into the image while it is happening (ephemeral image debuuging)
[20:20] <roaksoax> https://lists.launchpad.net/maas-devel/msg00808.html
[20:21] <hazmat> CyberJacob, juju get-constraints will do it
[20:21] <arosales> roaksoax, thanks for the doc
[20:22] <CyberJacob> roaksoax: you want me to run that one?
[20:22] <hazmat> CyberJacob, does the juju bootstrap node have connectivity to the maas server?
[20:22] <roaksoax> CyberJacob: I'd first like to know after what process is that you are seeing that error. (I'm guessing is enlistment, before the node is registered in maas)
[20:23] <roaksoax> CyberJacob: you are having several different errors that lead me to believe it is enlistment failing for some reason, then trying to enlist again, and so on
[20:23] <hazmat> CyberJacob, at the moment juju is complaining that it can't connect to the maas server.. hence the provisioning agent log error -> Error interacting with provider: Connection was refused by other side: 111: Connection refused
[20:23] <CyberJacob> hazmat: found the issue
[20:23] <CyberJacob> hazmat: I was following the instructions in http://maas.ubuntu.com/docs/juju-quick-start.html
[20:24] <CyberJacob> which has "maas-server: 'http://localhost:5240'" in environments.yaml
[20:24] <CyberJacob> changed that to the ip of the MAAS server
[20:24] <CyberJacob> (with the port)
[20:24] <CyberJacob> and everything jumped into life after I pushed the settings
[20:24] <hazmat> CyberJacob, cool
[20:25] <arosales> nice
[20:25] <arosales> roaksoax, hazmat thanks for the debugging session help
[20:25] <CyberJacob> thanks guys!
[20:25] <CyberJacob> (or gals)
[20:25] <arosales> roaksoax, could you update http://maas.ubuntu.com/docs/juju-quick-start.html to add a note for the maas server URL
[20:26] <arosales> CyberJacob, good luck with maas/juju. Glad to see you are using it :-)
[20:26] <CyberJacob> arosales: I have no actual use for it, just messing arround
[20:26] <CyberJacob> arosales: next up I'm going to see what use I can find for OpenStack
[20:26] <arosales> CyberJacob, that in itself is a use
[20:27] <arosales> :-)
[20:27] <CyberJacob> I still don't see the advantage of OpenStack over Xen or vmWare
[20:27] <CyberJacob> but I deffinitely see the uses of MAAS
[20:28] <roaksoax> arosales: sure thing
[20:28] <arosales> roaksoax, specifically to note the mass-server URL can be ip of the MAAS server (as found in this case).
[20:29] <arosales> roaksoax, thanks :-)
[20:29] <arosales> CyberJacob, thanks for helping improve the docs
[20:29] <roaksoax> arosales: yteah though, those docs seem to be older ones and not from the latest branch
[20:29] <roaksoax> arosales: but the docs on the website *do* say this "You may need to modify the maas-server setting too; if you're running from the maas package it should be something like http://hostname.example.com/MAAS."
[20:29] <CyberJacob> arosales: docs fixed, juju working and Egypt without a President, all in one night!
[20:30] <arosales> and 4th of July tomorrow for the US
[20:31] <arosales> roaksoax, ah ok. That should be sufficent
[20:31] <arosales> *sufficient
[20:31] <arosales> roaksoax, thanks again
[20:32] <roaksoax> arosales: yeah, i guess people miss it sometimes and don't fully read that section :)
[20:32] <roaksoax> (including myself, I had to read couple times before I realized that was there :) )
[20:33] <arosales> ya I would probably fall into that group, lol
[20:33] <roaksoax> lol :)
[20:33] <arosales> roaksoax, thanks!
[20:33] <roaksoax> arosales: np!
[20:34] <arosales> roaksoax, while I am bugging you
[20:34] <arosales> :-)
[20:34] <roaksoax> shoot:)
[20:34] <arosales> what are your thoughts on adding  https://lists.launchpad.net/maas-devel/msg00808.html to a debug section on the maas docs
[20:35] <roaksoax> arosales: It has been added actually. They are in the 'docs/troubleshooting.rst' in the maas source
[20:36] <arosales> roaksoax, but not on the live docs at maas.u.c?
[20:36] <roaksoax> but not yet published. The latest doc is not published
[20:36] <arosales> ah ok
[20:36] <roaksoax> yeah
[20:36] <arosales> but in the queue which is good :-)
[20:37] <roaksoax> :)
[21:15] <CyberJacob> ok, so I'm still having issues
[21:15] <CyberJacob> ping arosales & hazmat :)
[21:21] <CyberJacob> think I found the error
[21:21] <CyberJacob> http://pastebin.ubuntu.com/5841664/
[21:47] <arosales> CyberJacob, sorry missed your ping
[21:47] <arosales> CyberJacob, still not deploying services?
[21:49] <CyberJacob> nope
[21:50] <CyberJacob> arosales: The agent-state for everything I deploy is still pending
[21:52] <arosales> CyberJacob, were you trying to expose the service or just deploying?
[21:52] <CyberJacob> just deploying
[21:52] <CyberJacob> though I did try an expose as well
[21:55] <arosales> the trace back ~looks~ like its coming from a juju expose.
[21:56] <arosales> Although the issue seems to be stemming from communication with the provider (maas)
[21:58] <arosales> CyberJacob, could you pastebin  pastebin a tail -n 200 of  /var/log/maas/maas.log and /var/log/juju/provisioning-agent.log on the juju bootstrap server again
[22:23] <CyberJacob> arosales: Just turned my server off for the night :)
[22:24] <CyberJacob> arosales: I'll grab it tomorrow for you
[22:24] <arosales> CyberJacob, ok just ping back in here when you are ready to resume debug
[22:24] <arosales> note US holidy the next couple of days
[22:25] <arosales> so may be quiter in here than usual.
[23:43] <hazmat> CyberJacob|Away, there are some folks on eu timezones that  will be around though (also in #maas)