[04:34] <mup> Bug #1376906 changed: arm* agents cannot call home, but amd64 can <armhf> <hs-arm64> <hs-arm64-maas-juju> <hs-moonshot-maas-juju> <maas> <maas-provider> <network> <juju-core:Expired> <https://launchpad.net/bugs/1376906>
[07:28] <perrito666> marcoceppi_:  around?
[07:28] <marcoceppi_> perrito666: kind of, what's up?
[07:28] <perrito666> marcoceppi_: priv
[08:13] <perrito666> marcoceppi_: I am pretty sure you forgot your "Ill come back in half an hour" promise to cloudbase
[08:14] <marcoceppi_> perrito666: I'm talking to design, I'll swing by in 15 minsisshhhhhh
[08:17] <perrito666> marcoceppi_: Guardare per credere.
[09:06] <jamespage> wallyworld_, hey - I know you are all sprinting but https://bugs.launchpad.net/juju-core/+bug/1443541 is causing us pain - we can't verify openstack on vivid right now
[09:06] <mup> Bug #1443541: juju 1.23b4 vivid panic: runtime error: invalid memory address or nil pointer dereference <openstack> <uosci> <juju-core:Triaged by ericsnowcurrently> <https://launchpad.net/bugs/1443541>
[09:07] <jamespage> and I have a rc to upload - but would like to have tested it first :-)
[09:08] <wallyworld_> jamespage: yeah, that one is on our radar - the guy to fix it just arrived from pycon, so hopefully we'll get something done today
[09:09] <wallyworld_> jamespage: there's also this vivid issue we're looking at, bug 1443440
[09:09] <mup> Bug #1443440: 1.23-beta4 sporadically fails autotests <local-provider> <mongodb> <systemd> <ubuntu-engineering> <vivid> <juju-core:Triaged by ericsnowcurrently> <https://launchpad.net/bugs/1443440>
[09:10] <jamespage> wallyworld_, awesome
[09:10] <jamespage> wallyworld_, glad to hear its in hand - just flagging it up :-)
[09:10] <wallyworld_> i'll keep you informed
[09:10] <jamespage> wallyworld_, thanks
[09:10] <wallyworld_> jamespage: yeah, sorry about delays, travel etc got in the way
[09:10] <jamespage> wallyworld_, np - completely understand
[09:52] <jw4> OCR, forward port of change that landed on 1.23 recently http://reviews.vapour.ws/r/1423/
[10:05] <perrito666> lately everyone is becoming really lazy with PR descriptions
[11:44] <jw4> perrito666, updated per your feedback:  http://reviews.vapour.ws/r/1423/
[11:44] <ericsnow> jamespage: FYI, I'm working on those two vivid juju bugs
[11:44] <ericsnow> jamespage: I'll keep you posted on the progress
[11:49] <jw4> perrito666, ta
[11:53] <mup> Bug #1443904 was opened: Apache-licensed code has been borrowed with violation of license requirements <juju-core:New> <https://launchpad.net/bugs/1443904>
[11:58] <perrito666> gsamfira_: ^^ that has your name all over it :p
[11:58] <perrito666> literally
[11:58] <coreycb> I'm trying to force a config-changed hook to fire from within an action.  is there a better way to do that than just calling the function directly?
[11:58] <perrito666> jw4: ^^
[11:59] <jw4> hmmm; unfortunately I don't think that will work very well right now coreycb
[12:00] <jw4> the issue is that Actions and Hooks are in the same Uniter loop
[12:00] <jw4> this is something that has come up before often; I want some time with fwereade to plan a solution
[12:01] <coreycb> jw4, ok, thanks for the info
[12:01] <jw4> coreycb, :-/
[12:14] <mgz> gsamfira_: http://www.dangermouse.net/esoteric/whenever.html
[12:16] <jw4> coreycb, fwereade says just invoke the hook script directly rather than trying to get the hook to run
[12:16] <jw4> ../../hooks/config-changed.py
[12:16] <jw4> or something like that
[12:17] <jw4> coreycb, or better yet refactor the hook and action code so that common functionality is available to both
[12:18] <coreycb> jw4, ok thanks.  I had some success with a few charms by just executing our decorated config-changed function, but then I ran into an error and chalked it up to some missing juju state, but perhaps I can just do that.
[12:19] <jw4> coreycb, hopefully... let me know how it goes
[12:19] <coreycb> jw4, ok
[12:33] <voidspace> dooferlad: https://github.com/juju/juju/compare/1.23...voidspace:1.23-environ-subnets.diff
[13:35] <mup> Bug #1443942 was opened: SNAT for externally routed traffic should be only for EC2 and for subnets in the VPC <juju-core:Triaged by dooferlad> <https://launchpad.net/bugs/1443942>
[13:50] <dooferlad> voidspace/TheMue: Could I get a review? http://reviews.vapour.ws/r/1428/
[14:34] <arosales> http://reports.vapour.ws/latest-bundle-and-charm-results
[15:04] <thumper> voidspace, tasdomas here is the branch lp:~thumper/charms/trusty/postregresql/actions
[15:06] <ericsnow> jamespage: FYI, those two vivid bugs have fixes committed
[15:06] <ericsnow> jamespage: let me know if there are any other problems like that
[15:54] <mup> Bug #1444037 was opened: juju-core 1.22.1 is not packaged in Ubuntu <block-proposed> <juju-core:New> <https://launchpad.net/bugs/1444037>
[16:04] <redelmann> Hi, is charmstore down? or im having some internal problems?
[16:57] <mup> Bug #1444066 was opened: First set-env for a var always results in a WARNING <juju-core:New> <https://launchpad.net/bugs/1444066>
[18:32] <mbruzek> Hello gui guys.  What the heck is this? https://jujucharms.com/requires/ice-cream
[18:33] <mbruzek> brownies, raspberry sauce, marshmallows ??
[18:33] <mbruzek> benji ^
[18:34] <benji> we were hungry
[18:35] <benji> (it was for an [ill-conceived] demo)