[00:04] <thumper> wallyworld: this too https://github.com/juju/juju/pull/6186
[00:04] <thumper> now lunch
[00:04] <wallyworld> thumper-lunch: you can tell rb tp pick it up using rbt post
[00:07] <wallyworld> menn0: a whole lot of tests in api/controller/controller_test.go are no longer there with the various new migration tests being introduced. did you move them anywhere?
[00:08] <menn0> wallyworld: yep.. see legacy_test.go in the same package
[00:08] <menn0> legacy_test.go
[00:08] <wallyworld> ah righto thanks
[00:08] <menn0> weird ... the underscore doesn't show up for me :)
[00:09] <menn0> wallyworld: the migration tests couldn't work any more when using JujuConnSuite so I set things up for moving these tests to using a mock API
[00:09] <wallyworld> sgtm
[00:14] <mup> Bug #1474607 changed: worker/uniter/relation: HookQueueSuite.TestAliveHookQueue failure <ci> <go1.5> <go1.6> <regression> <windows> <juju:Fix Released by axwalk> <juju-core:Invalid> <juju-core 1.25:Won't Fix> <https://launchpad.net/bugs/1474607>
[00:19] <perrito666> you know where your day is going when you find yourself reading the code for mongo tools
[00:33] <anastasiamac_> wallyworld: could u please answer user question on https://bugs.launchpad.net/juju/+bug/1620886? :D
[00:33] <mup> Bug #1620886: juju status returns  ERROR connection shutdown <juju:Incomplete> <https://launchpad.net/bugs/1620886>
[00:33] <wallyworld> don't have time right now
[00:33] <wallyworld> maybe tomorrow
[00:34] <wallyworld> need to get beta ready
[00:34] <redir> what's this mean? http://juju-ci.vapour.ws:8080/job/github-merge-juju/9120/console at the end
[00:34] <redir> the bot failed to merge but it tried to?
[00:36] <redir> sinzui: ^^
[00:36] <redir> if your around
[00:37] <anastasiamac_> axw: could u plz comment on the bug wallyworld cannot? ^^
[00:38] <wallyworld> anastasiamac_: it will take analysis and investigation
[00:38] <wallyworld> can it wait till tomorrow?
[00:38] <wallyworld> we need to concentrate on the beta today
[00:38] <anastasiamac_> wallyworld: did u read the bug? it's a simple question...
[00:39] <wallyworld> "I sthere a way i can bring the model back"
[00:39] <wallyworld> that is a can of worms
[00:39] <wallyworld> he started on beta12
[00:39] <wallyworld> we made incompatible changes in 13/14
[00:40] <wallyworld> he will likely need to hand edit yaml files
[00:40] <anastasiamac_> i've read the bug. to me the answer is simple "no" he'll have to re-bootstrap. but u and andrew r more fmailiar with the area
[00:40] <anastasiamac_> i'll assign to u \o/
[00:40] <wallyworld> no thanks :-)
[00:40] <wallyworld> don't have time right now
[00:40] <anastasiamac_> who does?
[00:40] <wallyworld> no one today
[00:40] <wallyworld> beta take priority
[00:41] <sinzui> balloons: You need to follow up with http://juju-ci.vapour.ws:8080/job/github-merge-juju/9120/console the merge failed, but the tests passed and the job itself reports success.
[00:41] <wallyworld> let's see who's free tomorrow
[00:41] <sinzui> redir: have you tried to force your branch to merge?
[00:41] <redir> sinzui: don't know how
[00:42] <sinzui> redir: okay. I am taking a guess I will pretend to be jenkins on that host and run the failing command
[00:42]  * redir checks wiki
[00:43] <sinzui> redir: "Pull Request successfully merged"
[00:43] <redir> thanks sinzui-bot
[00:44] <sinzui> redir: ballons There must have been a network hiccup. running the command again took a second to complete
[00:45] <redir> sinzui: balloons I've noticed some slow GH action for the last 12h or so
[01:26] <redir> wallyworld: I moved the api bits here: https://github.com/reedobrien/juju/tree/feature/move-model-defaults
[01:26] <wallyworld> righto
[01:27] <wallyworld> i'll look when i can
[01:27] <redir> wallyworld: but haven't had time to make anything useful of moving the command bits yet
[01:27] <redir> and I have to go RSN
[01:27] <wallyworld> sure, np, i can pick it up
[01:27] <wallyworld> ty
[01:29] <redir> later juju-dev
[01:47] <axw> wallyworld: please see replies on http://reviews.vapour.ws/r/5618/
[01:47] <wallyworld> ok
[01:48] <wallyworld> axw: all good, i was thinking the calling code would test for ErrExpired, but wasn't sure how it would be used
[01:49] <axw> wallyworld: we check for NotFound atm, but not ErrExpired. it will make sense to do so when we have browser logins. because the client would pop up a browser and then go to the /auth/wait page straight away
[01:49] <axw> wallyworld: it would find the interaction, but it *would* be expired if the user doesn't hit login inside 2 minutes
[01:49] <wallyworld> yep
[01:54] <natefinch> Whazzat?  2016-09-08 01:48:00 ERROR cmd supercommand.go:458 failed to initialize state: validating initialization args: mismatching uuid (2eb2f71a-00d1-43db-8575-2d4eacb2bf3f) and controller-uuid (4d5116b1-945a-46af-8a27-69e7269d2753) not valid
[01:55] <natefinch> I saw some stuff go by on email/irc about UUIds... what's going on here?  I'm bootstrapping with a client from master, but trying to deploy beta17 .... is that broken, or did I do something wrong?
[01:55] <anastasiamac_> menn0: is there anything in rsyslog on 1.25 that would have caused this? u/thumper were going to check but i have not seen an update... https://bugs.launchpad.net/juju-core/1.25/+bug/1616832
[01:55] <mup> Bug #1616832: manual environment juju-db timeout <manual-provider> <juju:Incomplete> <juju-core:Won't Fix> <juju-core 1.25:Incomplete> <https://launchpad.net/bugs/1616832>
[01:58] <axw> wallyworld: you ok with that branch landing then?
[01:58] <wallyworld> yep
[01:59] <wallyworld> natefinch: yep broken
[01:59] <axw> thanks
[01:59] <wallyworld> natefinch: that's we we strictly enforce client and agent version match
[02:00] <natefinch> wallyworld: I thought we explicitly didn't do that, so you can use one client with multiple controllers that might be at different versions.... or is this just unique to bootstrap itself?
[02:00] <wallyworld> just bootstrap
[02:00] <wallyworld> the version check is just for bootstrap
[02:01] <natefinch> Is this unique just to this one point in time, where pre-beta18 servers won't work with post beta18 and later clients, or is this a new policy in general?
[02:03] <wallyworld> it happened between beta17 and 18
[02:03] <natefinch> ok
[02:03] <wallyworld> it's not a policy
[02:03] <natefinch> ok
[02:03] <wallyworld> but we don't guarantee client N can bootstrap agent N+1
[02:03] <wallyworld> it works 99% of the time
[02:03] <wallyworld> it betas, we are less strict about checking for such compatibility
[02:04] <natefinch> yep
[02:12] <menn0> anastasiamac_: NFI what's going on with that rsyslog issue
[02:12] <menn0> anastasiamac_: digging some more
[02:13] <anastasiamac_> menn0: thnx :)
[02:17] <menn0> anastasiamac_: hmmm... I think I've found something
[02:17]  * menn0 digs more
[02:18] <thumper> very simple review: http://reviews.vapour.ws/r/5623/ only adds logging
[02:19] <anastasiamac_> menn0: \o/
[02:19]  * anastasiamac_ hopes menn0 found the reason for cpu/mem spikes on 1.25 and will solve all world problems!!
[02:20] <menn0> anastasiamac_: I doubt this has anything to do with cpu/mem spikes :)
[02:20] <anastasiamac_> menn0: i know but m mentioning to see who else is watching :D
[02:21] <menn0> anastasiamac_: here's a helpful article: http://b.kl3in.com/2011/10/ubuntu-server-slowly-stops-responding/
[02:22] <menn0> anastasiamac_: it seems that if syslogd/rsyslogd hangs and stops reading from /dev/log then the buffer fills up as processes keep writing out logs, and when that happens processes start hanging when they try to log
[02:23] <menn0> anastasiamac_: i'm trying that out now
[02:23] <anastasiamac_> menn0: this is so sad :(
[02:23] <menn0> yeah, that's pretty awful
[02:24] <anastasiamac_> menn0: definitely worth adding to the bug and marking as Invalid for juju... ther is nothing we can really do on our side :(
[02:24] <menn0> anastasiamac_: well there is... we can have something that checks if rsyslogd is wedged and restart it when it is
[02:24] <menn0> anastasiamac_: there's a suggested script in the blog article
[02:25] <menn0> anastasiamac_: it's also possible that juju generated an invalid rsyslog config (or cert) which was causing it not to be able to work
[02:27] <anastasiamac_> menn0: both of which are gr8 suggestions and should b mentioned in the bug..
[02:27] <menn0> anastasiamac_: just doing a bit more research and then I'll update the bug
[02:28] <anastasiamac_> menn0: awesome \o/ if u could add how much effort would be involved in resolving these, it'll help power-that-be to plan.
[02:28] <menn0> ok
[02:29] <anastasiamac_> menn0: i'll also add an eda tag to it in hopes that QA may come up with functional test to reproduce it \o/
[02:39] <axw> wallyworld: external user login support: http://reviews.vapour.ws/r/5624/
[02:39] <wallyworld> axw: awesome, am about to ptopose a PR and then i'll look at the remaining PRs of yours
[02:39] <axw> thanks
[02:44] <mup> Bug #1557769 changed: private-address returns name, not ip, under 1.25.4 <Charm Helpers:In Progress by stub> <juju:Triaged> <juju-core:Invalid> <juju-core 1.25:Triaged> <cassandra (Juju Charms Collection):Fix Released by stub> <https://launchpad.net/bugs/1557769>
[02:44] <mup> Bug #1577556 changed: unit failing to get unit-get private-address in the install hook <intermittent-failure> <network> <juju:Triaged> <juju-core:Invalid> <juju-core 1.25:Triaged> <ubuntu-openstack-ci:Triaged> <mysql (Juju Charms Collection):Fix Released> <https://launchpad.net/bugs/1577556>
[02:58] <natefinch> wallyworld: I don't even seem to be able to juju status from current master client to beta17 server.  is that expected?
[02:59] <wallyworld> yes
[02:59] <natefinch> ok
[02:59] <wallyworld> controller and controller model uuids are now different
[02:59] <wallyworld> they used to be the same
[02:59] <wallyworld> hence not uuids by definition
[02:59] <natefinch> well, they are uuids... just not of the same thing :)
[03:00] <wallyworld> natefinch: note, with tools etc, the bootstrap messages always tell you what has been done so there are no surprises
[03:00] <natefinch> wallyworld: yes, but it's buried in there if you're using --debug
[03:01] <wallyworld> that  is true, debug is a firehose
[03:07] <thumper> axw: got a few minutes?
[03:08] <axw> thumper: yeah?
[03:08] <thumper> looking at a storage bug and I want to get ideas on how to test and if I'm doing it right
[03:08] <thumper> 5 min hangout?
[03:08] <axw> thumper: sure
[03:09] <thumper> axw: https://hangouts.google.com/hangouts/_/canonical.com/storge?authuser=0
[03:18] <wallyworld> axw: or thumper: or anyone, here's a PR I'd like to land today if anyone has time to review at some stage http://reviews.vapour.ws/r/5625/
[03:25] <natefinch> wallyworld: I can look at it
[03:25] <wallyworld> yay, ty
[03:34] <natefinch> anastasiamac_ (or anyone else) - what should I mark a bug assigned to me that appears to have been fixed, though perhaps not intentionally, and not by me?  Fix committed?
[03:34] <anastasiamac_> natefinch: of course \o/
[03:34] <natefinch> anastasiamac_: ok :)
[03:35] <anastasiamac_> natefinch:  it'll help if u knew PR that fixed it but otherwise, unless u r happy to field questions around the bug, keep it assigned to u
[03:35] <natefinch> anastasiamac_: yeah, I have no idea. I could repro in beta 17 reliably, can't in master.  ¯\_(ツ)_/¯
[03:36] <anastasiamac_> natefinch: best kind of bug :D
[03:37] <anastasiamac_> natefinch: well done \o/
[03:41] <axw> wallyworld: http://reviews.vapour.ws/r/5620/ has already been looked over by mhilton and ashipika, so I'll stick with just your review if that's ok?
[03:42] <wallyworld> axw: sure, np, just making sure
[04:11] <natefinch> wallyworld: lol, took me a while to figure out what hoak meant
[04:14] <wallyworld> lol
[04:14] <wallyworld> i can tweak that
[04:14] <natefinch> er haok
[04:15] <natefinch> wallyworld: I didn't have a better suggestion, so I was going to ignore it, but it was kinda funny.
[04:16] <natefinch> wallyworld: one thing - I kinda wonder if we'll make people worry if they see 3/4 machines for HA, when really, that fourth machine is hasvote: false wantsvote: false
[04:17] <natefinch> wallyworld: I don't know if it's really fixable, it's a lot of info to cram into a single column
[04:17] <wallyworld> natefinch: wantsvote false is not supposed to show
[04:18] <natefinch> wallyworld: oh, I misread the test I was looking at.. You're right.  Nevermind
[04:19] <wallyworld> natefinch: the 2/3 format is the same as is used for the scale column in status
[04:19] <wallyworld> i just made it up as a compact way to display
[04:19] <wallyworld> this betas will get feedback on that
[04:19] <wallyworld> and we'll tweak as needed
[04:22] <natefinch> cool
[04:22] <thumper> axw: testing our fix now on canonistack
[04:22] <axw> cool
[04:29] <natefinch> wallyworld: you have a review
[04:30] <wallyworld> natefinch: awesome, ty
[04:30] <wallyworld> natefinch: i had better fix any issues before you disappear
[04:30] <anastasiamac_> menn0: and since today is an rsyslog, just found this pearl :) https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1318378
[04:30] <mup> Bug #1318378: rsyslog starts dropping connections in large environments <logging> <rsyslog> <scalability> <sm15k> <juju-core:Triaged> <juju-core (Ubuntu):Triaged> <https://launchpad.net/bugs/1318378>
[04:35] <menn0> anastasiamac_: that one is probably fixable by tweaking rsyslogd's config or raising process limits
[04:36] <menn0> anastasiamac_: as for the first one, I've demonstrated that if rsyslogd is stuck, anything logging to it will get stuck.
[04:36] <menn0> anastasiamac_: this will be mongodb and in 1.25, all the agents in the model
[04:36] <anastasiamac_> \o/
[04:36] <anastasiamac_> these bugs are crying for ur comments ;)
[04:36] <menn0> writing up now
[04:40] <anastasiamac_> natefinch: if u r still here, thumper: i *think* this has been fixed coz we do not run mond as sudo.. right? https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1208430
[04:40] <mup> Bug #1208430: mongodb runs as root user <mongodb> <juju-core:Triaged> <juju-core (Ubuntu):Triaged> <https://launchpad.net/bugs/1208430>
[04:43] <natefinch> anastasiamac_: no idea... but uh... if they can 0 day the database.... whet else are we protecting?  The log files?  All the important data is *in* mongo :/
[04:46] <natefinch> ok, I gotta run, I'm passing out here.  wallyworld - changes LGTM
[04:46] <wallyworld> natefinch: awesome, tnas again
[04:46] <wallyworld> thanks
[04:50] <mup> Bug #1317909 changed: juju add-unit performance degrades in large environments <add-unit> <performance> <scalability> <sm15k> <juju:Triaged> <juju-core:Invalid> <juju-core (Ubuntu):Triaged> <https://launchpad.net/bugs/1317909>
[04:50] <mup> Bug #1318148 changed: Unit.PublicAddress shouldn't treat no machine as an error <landscape> <logging> <tech-debt> <ui> <juju:Triaged> <juju-core:Invalid> <https://launchpad.net/bugs/1318148>
[04:50] <mup> Bug #1318378 changed: rsyslog starts dropping connections in large environments <logging> <rsyslog> <scalability> <sm15k> <juju-core:Triaged> <juju-core (Ubuntu):Triaged> <https://launchpad.net/bugs/1318378>
[05:03] <menn0> anastasiamac_: lots of detail added to bug 1616832
[05:03] <mup> Bug #1616832: manual environment juju-db timeout <eda> <manual-provider> <juju:Incomplete> <juju-core:Won't Fix> <juju-core 1.25:Incomplete> <https://launchpad.net/bugs/1616832>
[05:04] <menn0> anastasiamac_: it should probably be reopened against 2.0 b/c it could happen there too since mongod still logs to syslog in 2.0
[05:05] <menn0> anastasiamac_: it's probably less likely because we demand a lot less of rsyslogd in 2.0 though
[05:18] <wallyworld> axw: if you are free, here's a cut and paste review http://reviews.vapour.ws/r/5627/
[05:18] <axw> ok
[05:23] <mup> Bug #1318378 opened: rsyslog starts dropping connections in large environments <logging> <rsyslog> <scalability> <sm15k> <juju-core:Triaged> <juju-core (Ubuntu):Triaged> <https://launchpad.net/bugs/1318378>
[05:28] <wallyworld> thanks axw
[05:28] <axw> nps
[05:29] <thumper> axw: http://reviews.vapour.ws/r/5628/
[05:29] <axw> looking
[05:33] <thumper> I'm off now
[05:34] <thumper> axw: if you're happy, can you do the merge dance?
[05:34] <thumper> laters
[05:34] <axw> thumper: will do. later
[05:57] <axw> wallyworld: I missed something in my branch when I QAd before. need to make a small change, will ping you for a review soon. change-user-password isn't storing a macaroon, so you need to log in again after changing your password
[05:58] <wallyworld> sure np
[05:58] <wallyworld> axw: i assume you'l lupdate the release notes at EOD as well?
[05:59] <axw> wallyworld: yup
[06:24] <axw> wallyworld: http://reviews.vapour.ws/r/5620/diff/3-4/
[06:24] <wallyworld> looking
[06:26] <axw> wallyworld: I've just re-run through all the QA steps again, and also confirmed that "change-user-password && status" does not prompt you after the password is changed
[06:26] <wallyworld> great
[06:28] <wallyworld> axw: lgtm, good that you found it
[06:29] <axw> wallyworld: thanks
[07:17] <mup> Bug #1554436 changed: Juju adds any RFC1918 address it finds on any state servers to the apiaddresses list in agent.conf <canonical-bootstack> <network> <juju:Triaged> <juju-core:Won't Fix> <https://launchpad.net/bugs/1554436>
[08:39] <axw> wallyworld: there's a problem with "juju logout" which I was planning to defer, but maybe shouldn't. if you "juju logout", your cookie remains in the jar. then "juju login <user>" will use it again without you being prompted
[08:40] <axw> wallyworld: fixing it is going to take a bit, because there's an issue with persistent-cookiejar
[08:40] <wallyworld> axw: we can document as a known issue for this beta imo
[08:41] <axw> wallyworld: ok
[08:58] <babbageclunk> voidspace: ping
[09:03] <wallyworld> axw: not sur eif you have a minute for a trivial format fix http://reviews.vapour.ws/r/5630/
[09:15] <wallyworld> babbageclunk: or maybe you could take a peek at the above for me? it's trivial, and needed for the beta
[09:19] <babbageclunk> wallyworld: sure, looking now
[09:19] <wallyworld> you rock ty
[09:23] <babbageclunk> wallyworld: LGTM!
[09:24] <wallyworld> babbageclunk: yay, ty. btw, it seems you finally got the right person from maas to talk to?
[09:24] <wallyworld> jeez, what a saga
[09:25] <babbageclunk> wallyworld: Yup - ripped out all my bodges and put in the right thing really easily, working on the provider changes now.
[09:25] <wallyworld> babbageclunk: sigh, how frustrating. seems like only a couple of people knew this secret knowledge
[09:26] <babbageclunk> wallyworld: Well, it was there in the docs, but I never searched with a keyword that matched it.
[09:27] <wallyworld> well, i didn't know the magic word either
[09:28] <babbageclunk> wallyworld: It's good though - the hacked version would've been nasty.
[09:28] <wallyworld> indeed, but it's all we thought we had :-)
[09:33] <frankban> axw: could you please take a look at http://reviews.vapour.ws/r/5631/ ?
[09:34] <axw> frankban: looking
[09:34] <frankban> axw: ty
[09:37] <axw> frankban: LGTM, thanks
[09:37] <frankban> axw: cool thanks
[10:15] <voidspace> babbageclunk: pong, sorry
[11:23] <babbageclunk> dimitern: around?
[11:25] <dimitern> babbageclunk: yeah?
[11:26] <babbageclunk> dimitern: I'm trying to test something on AWS, but I lost my credentials when my machine crashed - actually, might have just found an email, hangon.
[11:27] <babbageclunk> dimitern: Remind me of the url for the AWS console?
[11:27] <dimitern> babbageclunk: I remember sending the shared AWS account creds by mail a while ago, but might have missed you
[11:28] <dimitern> babbageclunk: pm-ed you the link
[11:28] <babbageclunk> dimitern: awesome, thanks
[11:33] <babbageclunk> voidspace, dimitern, frobware: Could someone take a look at this PR? https://github.com/juju/gomaasapi/pull/57
[11:33] <voidspace> babbageclunk: looking
[11:34] <babbageclunk> voidspace: thx!
[11:38] <voidspace> babbageclunk: so if args.OwnerData is nil then the iteration in ownerDataMatches just drops through to true
[11:38] <voidspace> babbageclunk: it seems a bit weird to call the filtering function even when there's no filtering
[11:38] <voidspace> babbageclunk: it's not wrong, just feels like the code doesn't match the user intent
[11:38] <voidspace> babbageclunk: only a slight niggle
[11:38] <voidspace> boiler repair man here, have to let him in
[11:40] <babbageclunk> voidspace: I think it does match the intent, though - a nil filter should match any owner data, right?
[11:45] <voidspace> babbageclunk: to me a nil filter means "don't bother checking"
[11:46] <babbageclunk> voidspace: I prefer not to have a different control flow (like an early exit) if the normal path through the block does the right thing.
[11:48] <babbageclunk> voidspace: But I don't feel super-strongly about it in this case. I can add `args.OwnerData != nil &&` on the start.
[11:49] <voidspace> babbageclunk: I don't feel strongly, it's a matter of taste and it's your code
[11:49] <voidspace> babbageclunk: so fair enough :-)
[11:50] <babbageclunk> voidspace: ok cool - I tried it and I don't like it. :)
[11:50] <voidspace> hah
[11:51] <dimitern> babbageclunk: sorry otp - looking though
[11:51] <babbageclunk> dimitern: no rush - I'm not blocked on it.
[11:51] <babbageclunk> dimitern: thanks though!
[11:53] <babbageclunk> dimitern: Actually, I just realised I can't make myself a new access key for AWS - can you make me a new one and invalidate the old one? Or do I need jam or someone else?
[11:55] <voidspace> babbageclunk: you don't explicitly test the nil case in new tests, is that because it's covered by the existing ones?
[11:56] <babbageclunk> voidspace: Yeah - if it didn't work then they wouldn't get any machines back.
[11:56] <voidspace> babbageclunk: cool, LGTM
[11:56]  * babbageclunk successkid
[11:56] <dimitern> babbageclunk: sure, just give me a few minutes
[12:12] <dimitern> babbageclunk: sent you new kets
[12:12] <dimitern> keys
[12:20] <voidspace> gah
[12:20] <voidspace> juju deploy stuck in allocating/pending and nothing in the debug-log and can't ssh
[12:20] <voidspace> need moar logging
[12:20] <rick_h_> voidspace: is this with tip?
[12:21] <rick_h_> voidspace: shooting you an email please see if thisis what you're seeing
[12:21] <voidspace> rick_h_: it  is, but it's also with a custom charm on lxd to test an interrupted sleep action
[12:21] <voidspace> rick_h_: ah, does look a bit like it yes
[12:22] <voidspace> rick_h_: I have an ipv6 address! but I can ssh into that
[12:22] <rick_h_> fwereade: ping
[12:23] <voidspace> and no juju logs on the system
[12:24] <rick_h_> fwereade: important email your way please
[12:58] <rick_h_> voidspace: so looking more closely at things, that email is only when HA is turned on close to when a deploy is in progress.
[12:59] <rick_h_> voidspace: just testing a bootstrap/deploy without HA isn't an issue and I'm assuming you're not in HA for your testing
[12:59] <dimitern> babbageclunk: reviewed
[12:59] <rick_h_> voidspace: so thinking there's different things goin on between your setup and the email thread there
[12:59] <babbageclunk> dimitern: thanks!
[13:12] <babbageclunk> frobware: Sorry, just realised I merged that without waiting for an all-clear from you - were you alright with that change other than the comment you made?
[13:15] <rick_h_> voidspace: ok, betting that marcoceppi's upcoming email to the juju list is your issue.
[13:15] <rick_h_> voidspace: try http://paste.ubuntu.com/23147632/ and see if that unblocks you there
[13:16] <rick_h_> voidspace: heh and as bac points out the commands there are moved in trunk so need to use set-model-config as model-config is an alias for get-model-config
[13:17] <babbageclunk> dimitern: How can I get values into Config.ResourceTags() in a test?
[13:18] <dimitern> babbageclunk: what's Config.ResourceTags()?
[13:19] <babbageclunk> dimitern: It's a set of user-defined tags that get applied to instances when they're started by the provider.
[13:20] <dimitern> babbageclunk: ah, so the juju one, not the maas one
[13:20] <dimitern> babbageclunk: let me have a look
[13:20] <babbageclunk> dimitern: Yeah - I'm hooking it up to maas owner data now.
[13:22] <babbageclunk> dimitern: Ah, think I've found the answer in config.go: "Config holds an immutable environment configuration."
[13:22] <babbageclunk> dimitern: I can't. Alright, I'll create it with them instead.
[13:22] <dimitern> babbageclunk: yeah :) also config with "resource-tags" key is used to hold them
[13:31] <dimitern> rick_h_: hey
[13:31] <dimitern> rick_h_: I've noticed no HO link on the sync call
[13:32] <rick_h_> dimitern: oh my bad
[13:32] <dimitern> rick_h_: and I'm sitting in the standup one
[13:32] <rick_h_> dimitern: k, I'll meet you there
[13:34] <babbageclunk> dimitern: Thanks!
[13:57] <babbageclunk> anyone seen alexisb this morning?
[13:57] <alexisb_> babbageclunk, I just sat down
[13:57] <alexisb_> omw
[14:00] <rick_h_> natefinch: ping for standup
[14:01] <dimitern> jam, fwereade: ^^
[14:06] <perrito666> morning all
[14:09] <dimitern> perrito666: o/
[14:22] <natefinch> ahasenack: btw, I couldn't repro https://bugs.launchpad.net/juju/+bug/1614635 with current master.  I could repro easily with beta17, so hopefully it just got fixed by something else.
[14:22] <mup> Bug #1614635: Deploy sometimes fails behind a proxy <deploy> <landscape> <proxy> <juju:Fix Committed by natefinch> <https://launchpad.net/bugs/1614635>
[14:45] <ahasenack> natefinch: got it
[14:45] <ahasenack> thx
[15:00] <voidspace> rick_h_: hah, just seen your IRC message telling me to try model-config instead of set-model-config :-)
[15:00] <rick_h_> voidspace: :)
[15:00] <voidspace> rick_h_: so, thanks...
[15:38] <redir> morning juju-dev
[15:41] <alexisb_> morning redir
[15:59] <redir> is there a qa list?
[15:59] <mgz> redir: yes, juju-qa@lists.canonical.com
[16:00] <mgz> you can always send things to it and can be manually moderated through, or you can join the fun
[16:00] <redir> thanks mgz
[16:01] <redir> I certainly don't get enough email as it is
[16:22] <rick_h_> dimitern: frobware ping, CI is seeing this failure: https://bugs.launchpad.net/juju/+bug/1621538 can we confirm that this is part of ongoing issues/work
[16:22] <mup> Bug #1621538: container networking: cannot juju ssh to container <ci> <maas-provider> <netowork> <regression> <juju:Triaged by dimitern> <https://launchpad.net/bugs/1621538>
[16:22] <rick_h_> dimitern: frobware and this started yesterday
[16:22] <rick_h_> dimitern: frobware it's blocking a beta18 as containers aren't working on maas
[16:23] <dimitern> rick_h_: looking
[16:26] <dimitern> 2016-09-08 13:55:23 ERROR juju.worker.proxyupdater proxyupdater.go:160 can't connect to the local LXD server: LXD socket not found; is LXD installed
[16:27] <dimitern> but yeah, apart from that - the root cause is: WARNING juju.provisioner lxd-broker.go:62 failed to prepare container "0/lxd/0" network config: host machine device "br-eth0" has no addresses
[16:29] <redir> alexisb: WRT https://goo.gl/yqrrPI what commands is the application config collapsing/replacing?
[16:30] <rick_h_> dimitern: ok, this is blocking beta18 and we need to get it turned around asap if we're going to try to release tomorrow
[16:31] <alexisb> redir,one sec
[16:31] <dimitern> rick_h_: we have 3 options - 1) ignore this until we land the rest of the PRs fixing bug 1566791, 2) temporarily disable functional-container-networking job (or make it non-voting), 3) revert frobware's bridge all PR and merge it back after beta18
[16:31] <mup> Bug #1566791: VLANs on an unconfigured parent device error with "cannot set link-layer device addresses of machine "0": invalid address <2.0> <4010> <cpec> <network> <juju:In Progress by dimitern> <https://launchpad.net/bugs/1566791>
[16:33] <frobware> dimitern: is this related to the the bridge all the world?
[16:33] <dimitern> frobware: yeah :/
[16:33] <dimitern> and only because of the way CI is configured
[16:33] <frobware> dimitern: I ran into issues too
[16:35] <rick_h_> dimitern: frobware can you all join https://hangouts.google.com/hangouts/_/canonical.com/rick?authuser=1
[16:36] <dimitern> not with authuser=1 I can't :)
[16:36] <rick_h_> dimitern: :P feel free to url edit
[16:38] <alexisb> ok redir, you have time for a HO?
[16:39] <perrito666> Bbl lunch
[16:44]  * rick_h_ goes for lunchables and such
[16:55] <redir> alexisb: yes
[16:55] <redir> if you still want to
[16:56] <alexisb> only if you need it redir
[16:57] <redir> alexisb: I am on track I think, thanks
[16:58] <redir> alexisb: at least for the next 10 minutes:)
[18:56] <babbageclunk> Is anyone else having problems adding machines with trunk? Mine just sit in pending.
[18:58] <rick_h_> babbageclunk: there's a message on the mailing list around it atm
[18:58] <babbageclunk> thanks rick_h_ - just saw that thread.
[18:58] <rick_h_> babbageclunk: https://lists.ubuntu.com/archives/juju/2016-September/007845.html
[19:14] <alexisb> babbageclunk, you still around?
[19:14] <babbageclunk> alexisb: yup yup
[19:14] <alexisb> babbageclunk meet hml
[19:14] <alexisb> she is helping us ou ton some api updates for openstack
[19:14] <alexisb> and had some qs around goose
[19:15] <babbageclunk> hi hml
[19:15] <alexisb> hml, babbageclunk may know given he just did some updates w/ goose
[19:15] <babbageclunk> uh, do I know anything about goose?
[19:15] <babbageclunk> I've been making changes to gomaasapi
[19:16] <alexisb> babbageclunk, ah that is right, my bad
[19:16] <alexisb> hml, ask anyways, we may get lucky :)
[19:16] <hml> hi babbageclunk
[19:16] <babbageclunk> I mean, I'll do my best!
[19:17] <hml> babbageclunk: is there a stratgey for version number changes? i’m looking at upgrading goose to use some newer api - like neutron.
[19:18] <rick_h_> babbageclunk: hml we've done that in the past with versioning the branch that the library is on so that you can rev the api with the branch and the dep pulls that branch
[19:19] <rick_h_> babbageclunk: hml see https://github.com/juju/charm for an example for a versioned lib like this
[19:20] <hml> thanks rick_h_
[19:21] <babbageclunk> thanks rick_h_ :)
[19:38] <babbageclunk> hey marcoceppi, are you the right person to ask for a review of https://code.launchpad.net/~2-xtian/charm-helpers/application-version-set/+merge/300183?
[20:18] <redir> back
[20:36] <marcoceppi> babbageclunk: sure, but you've got a competing implementation
[20:36] <rick_h_> fight fight!
[20:36] <babbageclunk> marcoceppi: doh!
[20:36] <rick_h_> I've got $5 on babbageclunk
[20:37] <marcoceppi> maybe not
[20:37] <alexisb> I will make it 50 on babbageclunk ;)
[20:37] <rick_h_> ooooh, the big players are dropping in
[20:37] <babbageclunk> (psst, marcoceppi, we could make a little moolah off these rubes.)
[20:38] <marcoceppi> well, you're up against lazypower ;)
[20:39] <marcoceppi> babbageclunk: you lost
[20:39] <marcoceppi> https://code.launchpad.net/~lazypower/charm-helpers/add-workload-version/+merge/305062
[20:39] <babbageclunk> It got merged yesterday! I totally should have chased a while ago.
[20:39] <marcoceppi> babbageclunk: and it had tests ;)
[20:40] <marcoceppi> rick_h_ alexisb pay up
[20:40]  * marcoceppi does an arbitrary release of charm-helpers
[20:41] <alexisb> darn it babbageclunk!
[20:41] <alexisb> I was counting on you ;)
[20:41] <perrito666> marcoceppi: 2.becauseIsaso.1 ?
[20:42] <rick_h_> marcoceppi: hah, owe you a beverage next week then
[20:42] <rick_h_> damn, didn't know I'd be up against lazypower.
[20:42] <rick_h_> never do that
[20:43] <marcoceppi> it was a close one
[20:43] <marcoceppi> 0.9.0 of charm-helpers is in pypi now, charm build will use it going forward and all charms will have access to it
[20:43] <marcoceppi> babbageclunk: thanks for contributing though!
[20:44] <babbageclunk> marcoceppi:  :) ah well, maybe next time!
[20:45] <babbageclunk> cool cool - I just deployed postgres and noticed that the version column wasn't filled in. I'll do a PR for using it in the charm.
[21:04] <marcoceppi> babbageclunk: yeah, we've been updating all of ours
[21:04] <babbageclunk> marcoceppi: nice
[21:05] <babbageclunk> morning menn0 - how's KiwiPyCon?
[21:06] <menn0> babbageclunk: hey hey... NFI, I'm not going until tomorrow. already had plans for tonight.
[21:06] <menn0> babbageclunk: how's things?
[21:06] <babbageclunk> menn0: pretty good!
[21:06] <babbageclunk> getting pretty stressed about the move
[21:08] <menn0> babbageclunk: yeah, it's not an easy thing, but it'll be done with soon enough
[21:12] <babbageclunk> menn0: looking forward to hanging out with the Tartleys on the way though.
[21:13] <menn0> babbageclunk: totally! how long are you with then?
[21:13] <menn0> them
[21:14] <babbageclunk> menn0: I think 4 or 5 days, should be cool
[21:16] <menn0> babbageclunk: that'll be awesome. z will be so different now I imagine.
[21:22] <alexisb> perrito666, ping
[21:22] <perrito666> alexisb: pong
[21:23] <alexisb> heya perrito666, what is going on with your current PR
[21:23] <alexisb> https://github.com/juju/juju/pull/6165
[21:23] <perrito666> alexisb: I forgot to push a missing file and am Just returning home (where the file is in my computer) right now working on the laptop
[21:23] <perrito666> apologies
[21:23] <alexisb> perrito666, ok, lets please get that landed
[21:24] <perrito666> aie
[21:50] <mup> Bug #1317896 changed: juju-restore requires mongodb-clients <backup-restore> <tech-debt> <juju-core:Fix Released> <juju-core (Ubuntu):New> <https://launchpad.net/bugs/1317896>
[22:00] <perrito666> alexisb: merged
[22:00] <alexisb> perrito666, thanks
[22:38] <voidspace> babbageclunk: hey, you there
[22:41] <menn0> axw or perrito666: https://github.com/juju/juju/pull/6198 pls
[22:42] <menn0> That's the result of me running go vet manually and realising we were missing stuff
[22:43] <perrito666> menn0: ship it
[22:43] <menn0> perrito666: thans
[22:43] <menn0> thanks
[22:43] <perrito666> menn0: tx for doing that
[22:51] <mup> Bug #1621658 opened: juju attach does not like to be canceled <juju-core:New> <https://launchpad.net/bugs/1621658>
[23:34] <babbageclunk> voidspace: wasn't but am now
[23:49] <babbageclunk> menn0: Mind doing a super-quick review? https://github.com/juju/gomaasapi/pull/58
[23:49] <menn0> babbageclunk: will do, almost done with standup
[23:49] <babbageclunk> or voidspace can ^^
[23:50] <babbageclunk> menn0: Oh yeah - I should have popped in.
[23:51] <menn0> babbageclunk: isn't it like crazy late for you?
[23:51] <babbageclunk> :(
[23:51] <babbageclunk> yeah, wanted to get something finished off, got a bit carried away.
[23:52] <menn0> babbageclunk: I get it :)
[23:52] <menn0> babbageclunk: LGTM on that change (although the correct change is really to fix the MAAS API - dashes are clearly superior to underscores :-D)
[23:53] <babbageclunk> menn0: I know, right?