[00:49] <jose> jcastro: I have classes, we need to coordinate so I can help you out
[03:00] <beisner> ping ctlaugh_
[06:09] <xenon_> hi there!
[08:39] <gnuoy> jamespage, have you got a sec for https://code.launchpad.net/~gnuoy/charm-helpers/nrpe-proxy/+merge/256626 ?
[09:09] <cmars> hi cory_fu
[09:09] <cory_fu> Hey
[09:09] <cmars> cory_fu, i think you're looking for code.google.com/p/rog-go/exp/cmd/godef
[09:09] <cory_fu> Thanks
[10:09] <jamespage> gnuoy, +1
[10:09] <gnuoy> Thanks
[10:33] <jamespage> gnuoy, just re-testing the freyes revised pxc HA improvements
[10:33] <gnuoy> kk
[11:01] <gnuoy> I've just upgraded from 1.22.1 to 1.23.0 (from proposed ppa) and after the upgrade I seem to have the same symptoms as Bug #1438489 which is fix committed.
[11:01] <mup> Bug #1438489: juju stop responding after juju-upgrade <upgrade-juju> <juju-core:Fix Committed by johnweldon4> <https://launchpad.net/bugs/1438489>
[11:11] <gnuoy> jw4, am I missing something or could that bug still be present?
[11:12] <jw4> gnuoy: I'm concerned that 1.23.0 doesn't have the latest 1.23 fixes
[11:12] <gnuoy> ah, that would be not be ideal
[11:13] <jw4> gnuoy: that change is in the 1.23 branch, but if you're seeing that error then the version of juju you upgraded to can't have that revision ....
[11:13] <jw4> I overheard an issue this morning where the deployed tarball was the wrong version
[11:14] <jw4> so it may be an issue that will be fixed soon
[11:16] <jw4> gnuoy: hmm; If I'm reading the milestones and releases right it might be fixed in 1.23.1 instead of 1.23.0
[11:16] <gnuoy> jw4, Does that mean that the tools juju plucked from streams.canonical.com  when I did the upgrade might not have had the fix
[11:16] <gnuoy> oh
[11:19] <jw4> gnuoy: no... the 1.23.0 tag DOES include my fix, so a recent install of 1.23.0 should work (if the tarball was right)
[11:20] <gnuoy> jw4, the tar ball you're referring to is the tools downloaded by juju from streams.c.c ?
[11:21] <jw4> gnuoy: I think so.. whichever mechanism delivers the actual jujud that is upgraded to.  One thing I noticed in your bug report... did you see that error message only once? or many times?
[11:21] <gnuoy> let me check, then env is still there
[11:21] <jw4> The 'fix' that I put in converted the hard error into just an error being logged once in the logfile but then continuing normally
[11:21] <gnuoy> s/then/the/
[11:22] <jw4> (so any other symptoms you're seeing may be unrelated to that specific bug)
[11:25] <gnuoy> jw4, I see that message once on each unit, and that appears to be the last message each unit reports
[11:25] <jw4> gnuoy: ok.. so it looks like my fix is in.
[11:25] <jw4> gnuoy: otherwise the message would just keep repeating infinitely.
[11:25] <jw4> gnuoy: what are the follow on symptoms you're seeing?  Hooks not firing at all?
[11:26] <gnuoy> jw4, but that message appears to be terminal, nothing happens after
[11:26] <gnuoy> jw4, right, silence in logs and no hook execution
[11:26] <jw4> gnuoy: I'll see if I can reproduce that.
[11:26] <gnuoy> jw4, thank you for all your help
[11:27] <jw4> gnuoy: thanks for reporting :)
[11:50] <jw4> gnuoy: I've reproduced the symptoms
[11:50] <jw4> gnuoy: I'll re-open that bug
[11:51] <gnuoy> jw4, that was quick, thanks!
[11:51] <jw4> gnuoy: thank the team when it's fixed ! :)
[17:51] <francokaerntna> hey, anybody of you know what I need to change in my juju config, so that I get 'public' ips in my maas environment?
[17:52] <francokaerntna> I entered both networks in maas 'network' tab, added 2 interfaces (one of each network) to the cluster, and even 'juju status' is showing me both networks. any clue?