[00:14] <davecheney> mwhudson: ok
[00:40] <natefinch> thumper: why do we use github.com/juju/schema instead of using struct tags?
[00:43] <davecheney> natefinch: jw4 might have an opinion
[01:00] <wallyworld> axw: can you recall the change in master that flattened storage.Volume ie got rid of VolumeInfo. i'm getting conflicts merging 1.24 and just need to recall which way around it is supposed to be in master
[01:12] <axw> wallyworld: it's hte other way around, I extracted VolumeInfo from Volume
[01:12] <wallyworld> axw: right, ty
[01:28] <natefinch> davecheney: note, I'm talking our own yaml schema validation stuff for like metadata.yml, not jsonschema, if that's what you were thinking.  Pretty sure the schema stuff predates jw4 :)
[01:49] <davecheney> oh
[01:49] <davecheney> right
[01:49] <davecheney> ignore what i said
[01:49] <davecheney> i thought you were watlkig about json schema
[02:21] <thumper> fuck fuck fuckity fuck
[02:50] <wallyworld> thumper: is jessie in today?
[02:51] <thumper> no, leave
[02:53] <wallyworld> thumper: ah ok, can you remind him next week then to port bug 1441478 to master, i think he forgot
[02:53] <mup> Bug #1441478: state: availability zone upgrade fails if containers are present <upgrade-juju> <juju-core:Triaged> <juju-core 1.24:Fix Released by waigani> <https://launchpad.net/bugs/1441478>
[02:54] <wallyworld> i could include it in my forward port, if i can do so without risk i will
[03:06] <menn0> wallyworld: an old ticket (bug 1318366) has recently been reopened by aaron regarding mgo/txn panics
[03:06] <menn0> wallyworld: it's attached to me b/c I helped fix last year's issue
[03:06] <wallyworld> oh?
[03:07] <menn0> wallyworld: I think fwereade is looking at this issue ("panic: rescanned document misses transaction in queue")
[03:07] <menn0> wallyworld: do you know?
[03:07] <wallyworld> yes he's looking
[03:07] <wallyworld> stuck though
[03:08] <menn0> wallyworld: found the newer ticket: https://bugs.launchpad.net/juju-core/+bug/1449054
[03:08] <mup> Bug #1449054: Intermittent panic: rescanned document <ci> <test-failure> <juju-core:Triaged by fwereade> <juju-core 1.22:Fix Released by dimitern> <juju-core 1.23:Won't Fix by fwereade> <juju-core 1.24:Fix Released by fwereade> <https://launchpad.net/bugs/1449054>
[03:08] <menn0> wallyworld: looks like the fix wasn't merged into trunk though
[03:09] <menn0> wallyworld: I might deal with this now b/c I want to bump the mgo dependency anyway
[03:10] <wallyworld> menn0: i'm forward porting a bunch of 1.24 vhanges now, which includes the latest mgo from 1.24. trunk has an old copy of mgo from a year ago
[03:10] <wallyworld> menn0: trunk will soon have the sme dep rev as 1.24
[03:11] <wallyworld> or did you want a later one as a new mgo has been released since then
[03:11] <menn0> wallyworld: I want something from the release from a few days ago
[03:11] <menn0> wallyworld: it's not urgent though
[03:12] <menn0> wallyworld: so do your forward port first and i'll handle bumping the dep again afterwards
[03:12] <wallyworld> ok, i'll hopefully have master up to date (mostly) with 1.24 soon
[03:25] <menn0> wallyworld: are we likely to ever do another 1.22 release? CI opened up a ticket for a test fix for 1.22 recently that we have fixed in later releases but it was never backported that far back. i'm think I can close it unless we might do another 1.22 release.
[03:25] <thumper> wallyworld: got time to hangout?
[03:26] <wallyworld> thumper: sure
[03:26] <thumper> back in our chat
[03:26] <wallyworld> kk
[03:26] <wallyworld> menn0: we might do a 1.22.6
[03:26] <wallyworld> menn0: but no decision yet - depends if william finds and fixes the mgo bug
[03:26] <wallyworld> menn0: so may keep open until decided
[03:27] <menn0> wallyworld: ok. i'll backport this fix. it's a fairly easy one.
[03:27] <wallyworld> ok
[04:14] <thumper> trivial review for someone: http://reviews.vapour.ws/r/1866/
[04:16] <davecheney> thumper: i shall put a trivial effort into reviewing said
[04:16] <thumper> davecheney: WFM
[04:19] <davecheney> i also added a trivial review comment
[04:19] <davecheney> it should be trivial for you to address same
[04:32] <menn0> wallyworld: you around?
[04:32] <wallyworld> yeah
[04:33] <menn0> wallyworld: see PM
[04:54] <wallyworld> axw: we you have a moment, could you eyeball this for me? it picks up our various 1.24 fixes for storage, leadership, etc, plus the tags stuff. diff is big, but if you know the work, you should be able to peruse through pretty quickly http://reviews.vapour.ws/r/1868/diff/#
[04:55] <axw> wallyworld: ok
[04:55] <wallyworld> no rush
[04:56] <axw> wallyworld: I found why the blockdevices txns are aborting: structs are in a different order in mongo to in the assertion. I have nfi how they got in that order though. current hypothesis is that mgo/txn is deserialising a queued transaction's ops into a bson.M, and so not preserving the order
[04:57] <wallyworld> oh wonderful
[04:57] <wallyworld> that could explain it yeah
[04:57] <wallyworld> axw: doesn't mongo order the struct fields alphabetically?
[04:58] <axw> wallyworld: no, it stores them in the order you present them. mgo preserves struct field order when encoding to BSON
[04:59] <wallyworld> ok, i recall something about alphabetically order, but can't remember now
[05:10] <axw> wallyworld: merge looks fine
[05:10] <wallyworld> axw: ty, will land and mark a lot ofbugs as fix committed
[05:29] <wallyworld> axw: reviewed, off for school pickup, bbiab
[05:29] <axw> wallyworld: thanks. heh, oops, left that && false for debugging
[05:29] <wallyworld> thought so :-)
[06:14]  * thumper is done
[06:51] <mup> Bug #1462213 opened: [Ubuntu Vivid] Cannot bootstrap on local provider <juju-core:New> <https://launchpad.net/bugs/1462213>
[06:59] <axw> wallyworld: bleh, I broke managedfs
[06:59] <axw> wallyworld: haven't merged, will fix that first
[06:59] <wallyworld> ok
[06:59] <wallyworld> phew
[08:35] <axw> wallyworld: FYI I've pushed my fix to the PR. tested manually, going to rebase and merge now
[08:43] <wallyworld> axw: great, ty
[11:41] <dimitern> voidspace, ping
[11:42] <dimitern> voidspace, because I keep forgetting, let me ask you now - please send me the ep2015 talk by mail so I can go over it :)
[11:48]  * dimitern steps out for a while
[11:56] <voidspace> dimitern: I have to find it
[11:56] <voidspace> dimitern: but yes - it's not on this computer
[11:57] <voidspace> dimitern: it's probably on my laptop - and I'm going downstairs to work as the handyman needs my office
[12:30] <perrito666> good morning all
[13:32] <natefinch> can someone else try logging on to canonicaladmin?  it keeps telling me the username and password is wrong, but they're saved in my password manager, so I'm sure they're not wrong
[13:33] <jhobbs> wfm natefinch
[13:33] <natefinch> hmm... possibly related: https://www.youtube.com/watch?v=Lz9810Y7ZRw
[13:34] <perrito666> natefinch: In a company I once worked that meant talk to rrhh :p
[13:34] <perrito666> yeah, exactly that video
[13:34] <perrito666> natefinch: works for me, still ugly as hell
[13:36] <natefinch> weird
[13:57] <natefinch> ericsnow: do we support vivid on 1.22?  re: https://bugs.launchpad.net/bugs/1462213
[13:57] <mup> Bug #1462213: [Ubuntu Vivid] Cannot bootstrap on local provider <juju-core:New> <https://launchpad.net/bugs/1462213>
[14:02] <mgz_> natefinch: no
[14:02] <mgz_> natefinch: not for the local provider specifically
[14:07] <mup> Bug #1462213 changed: [Ubuntu Vivid] Cannot bootstrap on local provider <juju-core:New> <https://launchpad.net/bugs/1462213>
[15:16] <mup> Bug #1462409 opened: FilesystemStateSuite setup failed <ci> <test-failure> <juju-core:New> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1462409>
[15:25] <mup> Bug #1462409 changed: FilesystemStateSuite setup failed <ci> <test-failure> <juju-core:Incomplete> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1462409>
[15:34] <mup> Bug # opened: 1462409, 1462412, 1462415, 1462417, 1462418
[15:37] <mup> Bug # changed: 1462412, 1462415, 1462417, 1462418
[15:42] <natefinch> katco: which hangout are we supposed to be in now?  I'm in retrospective, but no one else is
[15:42] <ericsnow> natefinch: we all went back to moonstone
[15:46] <mup> Bug # opened: 1462412, 1462415, 1462417, 1462418, 1462423
[16:32] <mup> Bug #1457645 changed:  warning: log line attempted over max size - leadership related <cloud-installer> <landscape> <mongodb> <juju-core:Fix Released by wallyworld> <juju-core 1.23:Fix Committed by wallyworld> <juju-core 1.24:Fix Released by wallyworld> <https://launchpad.net/bugs/1457645>
[16:53] <mup> Bug # changed: 1376246, 1431372, 1454678, 1454891, 1457728, 1459057, 1459060, 1459250, 1459611, 1459616, 1459885, 1459912, 1461111, 1461342
[17:35] <katco> ericsnow: wwitzel3: you 2 back yet?
[19:58] <marcoceppi> why doesn't this command work in 1.24-beta5? juju get-env admin-secret
[20:00] <marcoceppi> let me rephrase, how can I programatically get the password/admin-secret for an environment from the command line without doing `grep "admin-secret" ~/.juju/environments/gce.jenv | awk '{ print $2 }'`
[20:02] <rick_h_> marcoceppi: should you use the admin secret any more vs the password? can you programatically get the password?
[20:02] <alexisb> ericsnow, wwitzel3 ^^ any idea?
[20:02] <marcoceppi> rick_h_: I tried password
[20:02] <marcoceppi> it said that key does not exist
[20:02] <rick_h_> marcoceppi: oh hmm, might mention that one to thumper
[20:02] <marcoceppi> marco@galago:~$ juju environment get password
[20:02] <marcoceppi> ERROR key "password" not found in "gce" environment.
[20:03] <ericsnow> marcoceppi: is this a GCE-specific issue?
[20:03] <marcoceppi> this is every environment
[20:04] <ericsnow> k
[20:04] <rick_h_> yea, would guess no, more a general thing
[20:04] <marcoceppi> marco@galago:~$ juju environment get password
[20:04] <marcoceppi> ERROR key "password" not found in "aws-west-2" environment.
[20:04] <marcoceppi> also, environment doesn't accept an -e flag :(
[20:04] <marcoceppi> oh, but get does
[20:04] <marcoceppi> oops
[20:04] <natefinch> hahaha
[20:04] <ericsnow> ah, I don't know a ton about the new environment management stuff
[20:05] <marcoceppi> well, get-env has been around for a while
[20:05] <marcoceppi> probably the 1.18 days
[20:05] <natefinch> we were just talking about the -e stuff in a bug report
[20:05] <marcoceppi> which is an alias to environment get
[20:05] <natefinch> marcoceppi: https://bugs.launchpad.net/juju-core/+bug/1461605
[20:05] <mup> Bug #1461605: juju action commands require -e in the "wrong" place <actions> <improvement> <juju-core:Triaged> <https://launchpad.net/bugs/1461605>
[20:06] <natefinch> marcoceppi: the comments on the bug go beyond just actions thought
[20:06] <natefinch> s/thought/though
[20:06] <natefinch> basically all the new "double command" commands "action do" "environment get"  require the -e after the second command
[20:07] <marcoceppi> natefinch: cool, but I really just need to get the password programmatically now ;)
[20:07] <natefinch> heh
[20:07]  * marcoceppi goes back to just grep and awk though he's aware of some shake up around .jenvs
[20:12] <marcoceppi> behold. grep "admin-secret" ~/.juju/environments/$(juju switch).jenv | awk '{ print $2 }'
[21:19] <perrito666> my vim is all confused of having python in it again
[22:46] <marcoceppi> getting this error when trying to build in golang
[22:46] <marcoceppi> ../../../gopkg.in/juju/charm.v5/meta.go:19: import /home/marco/.go/pkg/linux_amd64/gopkg.in/juju/charm.v5/hooks.a: object is [linux amd64 go1.2.1 X:none] expected [linux amd64 go1.3.3 X:precisestack]
[22:46] <marcoceppi> I have go 1.3.3 installed
[22:47] <marcoceppi> not sure what I did or how to fix this
[22:48] <gsamfira> marcoceppi: rm -rf $GOPATH/pkg
[22:48] <gsamfira> and try again
[22:48] <marcoceppi> gsamfira: I ended up blowing away charm.v5 and re-getting it
[22:49] <marcoceppi> seemed to sort it, thanks
[22:49] <marcoceppi> I'm trying to print a reference
[22:49] <marcoceppi> because I want to know what it's about and I can't figure it out normally, "cannot use ref (type *charm.Reference) as type string in argument to fmt.Printf" so obviously Printf isn't my friend