[00:02] <mup> Bug #1563117 opened: api: data race adding local charm. <juju-core:New> <https://launchpad.net/bugs/1563117>
[00:14] <mup> Bug #1563117 changed: api: data race adding local charm. <juju-core:New> <https://launchpad.net/bugs/1563117>
[00:17] <mup> Bug #1563117 opened: api: data race adding local charm. <juju-core:New> <https://launchpad.net/bugs/1563117>
[01:55] <natefinch> is it just me, or is reviewboard broken?
[01:55] <natefinch> I'm not actually getting any diffs, just spinners that spin forever
[01:57] <mup> Bug #1558769 changed: unable to create-model in azure <juju-core:Fix Released by axwalk> <juju-core admin-controller-model:Fix Released by axwalk> <https://launchpad.net/bugs/1558769>
[01:57] <natefinch> hmm, no, maybe it's just the two specific reviews I was looking at. Weird.
[01:58] <axw> natefinch: not just you
[01:59] <natefinch> axw: ok, cool
[01:59] <axw> natefinch: I got some errors about it being out of space
[01:59] <natefinch> ahh
[01:59] <axw> looks like /tmp is full
[01:59] <natefinch> that would explain why some work and some don't, if some got cached or somethnig
[03:30] <mup> Bug #1545589 changed: Destroying a model leaves stale current-model file <destroy-environment> <juju-release-support> <juju-core:Fix Released> <https://launchpad.net/bugs/1545589>
[03:46] <axw> thumper: https://bugs.launchpad.net/juju-core/+bug/1534627 -- what's expected here? I vaguely recall Jess saying that models hang around after being "destroyed", and aren't actually removed from the DB until some time later
[03:46] <mup> Bug #1534627: Destroyed models still show up in list-models <conjure> <juju-release-support> <juju-core:Triaged> <https://launchpad.net/bugs/1534627>
[03:47] <thumper> axw: yes, the actual docs stay around so they can be queries, retrieved
[03:47] <thumper> axw: we should either show the model as dead
[03:47] <thumper> or not show it by default
[03:47] <thumper> I think by default we should just show alive models
[03:47] <axw> thumper: why do we do that? we don't do it for anything else
[03:48] <thumper> axw: because models are special, and it is handy to be able to watch them die
[03:48] <thumper> post mortemts etc
[03:48] <thumper> list models in apiserver should provide life or skip non-alive
[03:49] <axw> okey dokey
[03:49] <axw> thumper: and if someone tries to create a model with the same name?
[03:50] <axw> I wonder if we shouldn't disassociate the name when it's destroyed, so you can still reuse the name
[03:50] <thumper> IIRC we were going to have dead ones possibly renamed or only look for alive ones...
[03:50] <thumper> it is expected that you should be able to reuse the name
[03:50] <thumper> somehow
[03:50] <axw> ok
[04:18] <mup> Bug #1538652 changed: MAAS doesn't assign DHCP IP to new Node and doesn't update DNS table <maas-provider> <juju-core:Expired> <https://launchpad.net/bugs/1538652>
[04:51] <davecheney> https://bugs.launchpad.net/juju-core/+bug/1561375
[04:51] <mup> Bug #1561375: state: TestRegisterNoSecretKey unreliable <juju-core:Triaged> <https://launchpad.net/bugs/1561375>
[04:51] <davecheney> booo
[04:51] <davecheney> this is an upsream break
[04:51] <davecheney> go 1.6 is fine
[04:52] <davecheney> i'll log a bug upstream and let them deal with it
[05:23] <cherylj> could I get a trivial review from someone?  https://github.com/juju/juju/pull/4906
[05:31] <davecheney> no bot ?
[05:31] <davecheney> LGTM
[09:32] <TheMue> morning o/
[09:37] <frobware> fwereade_: space discovery... I was just trying to understand where this ended up in terms of when it was blocked... and not. I was running some git bisect script which added a container after bootstrap but my script often barfed because "spaces discovery is still in progress".
[09:47] <fwereade_> frobware, oops, sorry: how can I help?
[09:48] <fwereade_> frobware, I'm not sure what the current state of master -- I presume it's doesn't-block-logins-reliably? -- but MADE-model-workers doesn't try to block logins at all
[09:49] <fwereade_> frobware, and I haven't seen a merge conflict that looked related
[09:51] <fwereade_> frobware, IIRC that was where we left it when I hit it last time; I'm not opposed to login-blocking in itself, but if it doesn't actually block all problematic logins it's kinda pointless
[09:53] <babbageclunk> Gah, any way to see chat messages from a hangout after one has left the hangout? :( I mean, I can remember --upload-tools but it seemed like there was probably other useful info in there.
[09:55] <frobware> fwereade_: can we briefly HO to talk about it?
[10:01] <fwereade_> frobware, sure, back in standup?
[10:01] <frobware> fwereade_: yep
[10:26] <babbageclunk> Sweet, bootstrapped (although I got a warning about "space discovery still in progress" as well).
[10:39] <babbageclunk> voidspace: trying to deploy juju-gui to my cloud, I get this: ERROR storing charm for URL "cs:trusty/juju-gui-52": cannot retrieve charm "cs:trusty/juju-gui-52": cannot get archive: Get https://api.jujucharms.com/charmstore/v5/trusty/juju-gui-52/archive: dial tcp: lookup api.jujucharms.com on 192.168.100.2:53: no such host
[10:41] <babbageclunk> I can get that url on the maas controller (which is 192.168.100.2). I haven't been able to ssh into the juju controller (which is .17) - should I be able to?
[10:41] <babbageclunk> Ooh, just trying juju ssh.
[10:41] <babbageclunk> No, that didn't work.
[10:44] <babbageclunk> I was specifying the node wrong. I'm in - seeing if I can get the file from there.
[10:51] <voidspace> babbageclunk: yep, that's the thing to try
[10:52] <voidspace> babbageclunk: I'm *still* trying to get maas 2 working on this VM after it broke
[10:52] <voidspace> babbageclunk: a full remove kept failing, think I got it now and am re-installing
[10:52] <voidspace> babbageclunk: if not I'll just blow away the VM and start again
[10:52] <voidspace> babbageclunk: if this was automated it would be easier :-)
[10:54] <babbageclunk> voidspace: Ok, so it looks like the problem is that 192.168.17 (the juju node) has its nameserver set to .2 (the maas controller), while the maas controller (where the charm store request succeeds) has .1 as the nameserver.
[10:54] <voidspace> babbageclunk: how weird
[10:54] <voidspace> babbageclunk: that's set by maas in cloud-init I think
[10:54] <voidspace> babbageclunk: this is on 1.9
[10:54] <babbageclunk> voidspace: yes
[10:54] <voidspace> frobware: ^^^^ is this something you've seen?
[10:58] <babbageclunk> voidspace, frobware: maybe it's the fact that the cluster interface in the MAAS admin is set to be "DHCP and DNS"? Is that wrong?
[11:01] <voidspace> babbageclunk: no, that's correct
[11:02] <voidspace> babbageclunk: you could try just dhcp and see if that makes a different - I normally do both I think
[11:04] <frobware> fwereade_: http://rr-project.org/
[11:05] <babbageclunk> voidspace: ok. Best way to bounce a machine in juju?
[11:06] <babbageclunk> voidspace: should I just restart it from the maas ui?
[11:06] <voidspace> babbageclunk: try "juju reboot 1"
[11:06] <voidspace> babbageclunk: I'm kind of guessing
[11:06] <voidspace> babbageclunk: I normally bounce it in virt-manager
[11:06] <babbageclunk> voidspace: doh, missed that in the list.
[11:06] <voidspace> I knew we had a reboot command - for charms, wasn't 100% it was in the CLI
[11:07] <voidspace> manually restarting the machine restarts the machine agent anyway, so that's what I do
[11:08] <babbageclunk> voidspace: I went semi-scorched earth and did a destroy then bootstrap again.
[11:10] <fwereade_> babbageclunk, voidspace: I have a feeling that there's a bad interaction with juju-reboot, so I don't think you can juju run that, but you should be able to do something like `juju run --machine 2 "sudo shutdown -r now"`
[11:10] <fwereade_> babbageclunk, voidspace: hooks/actions can request reboots with juju-reboot though
[11:12] <voidspace> fwereade_: ah, thanks
[11:12] <babbageclunk> voidspace, fwereade_: despite being overkill, watching the bootstrap process again is giving me a bit better feel for what's happening (and which moving part is responsible for it), so it wasn't a complete loss.
[11:13] <fwereade_> babbageclunk, cool :)
[11:13] <fwereade_> babbageclunk, and ofc you could just `juju ssh 1` and do whatever you need there
[11:14] <babbageclunk> fwereade_: cool, thanks
[11:14] <fwereade_> babbageclunk, (and that should work even if the agent's having trouble, which can stymie juju run)
[11:20] <voidspace> hah, so MAAS was dying with internal server error
[11:20] <voidspace> spelunking in the logs found that going to the accounts page causes the web ui to attempt to shell out to bzr - which wasn't installed
[11:20] <voidspace> how odd
[11:22] <voidspace> babbageclunk: the "changing maas to not do dhcp over the whole subnet" may be new in a more up to date version of maas 2
[11:22] <voidspace> babbageclunk: I'm using the experimental3 ppa and when I configured dhcp I have to provide the range (which defaults to the whole subnet) which I didn't have to do previously
[11:23] <voidspace> babbageclunk: and I guess if it provides dhcp over the whole range then it has no static ips available
[11:25] <babbageclunk> voidspace: OK, so why can't my juju controller get to api.jujucharms.com? Is having the nameserver be the maas controller right?
[11:25] <voidspace> babbageclunk: that should be correct I believe
[11:25] <voidspace> frobware: ^^^
[11:26] <voidspace> babbageclunk: I have maas 2 running (finally I think - just trying enlisting) so can't check on 1.9
[11:26] <voidspace> just yet anyway
[11:31] <babbageclunk> voidspace, frobware: so presumably the problem is that the DNS server on the maas controller isn't responding correctly. I can see dnsmasq running on the maas controller.
[11:32] <voidspace> babbageclunk: it's not a problem I've had though
[11:32] <voidspace> babbageclunk: what if you try without maas providing dns
[11:32] <frobware> babbageclunk: can you deploy a node? If so, can you login to that node and resolve news.bbc.co.uk?
[11:33] <voidspace> frobware: he can deploy, but he then can't connect to the outside world
[11:33] <voidspace> I believe
[11:33] <frobware> voidspace, babbageclunk: where connect is just DNS?
[11:33] <babbageclunk> voidspace, frobware: that's right
[11:34] <frobware> babbageclunk: what do you have in your MAAS setup for upstream DNS queries?
[11:34] <frobware> babbageclunk: from the UI, choose "Settings", then part way down that page is ...
[11:34] <babbageclunk> frobware: checking now
[11:34] <frobware> babbageclunk: "Upstream DNS used to resolve domains not managed by this MAAS (space-separated IP addresses)"
[11:35] <frobware> babbageclunk: I have 192.168.1.1 (which is may gateway. You could add 8.8.8.8
[11:35] <babbageclunk> frobware: Aha - I've never seen that page before!
[11:35] <babbageclunk> frobware: I'll add the gateway there.
[11:35] <babbageclunk> frobware: (Also I'll add it to my setup notes.)
[11:36] <frobware> babbageclunk: it's not a gateway though (assuming we're talking about the same thing)
[11:37] <babbageclunk> frobware: Sorry - sloppy terminology on my part. I think I mean it's the KVM switch? It's what's in the resolv.conf on the maas controller (where the name resolves fine).
[11:38] <frobware> babbageclunk: so presumably .1
[11:38] <babbageclunk> frobware: that's right
[11:45] <frobware> babbageclunk: any joy?
[11:46] <babbageclunk> frobware: yes! juju-gui is deployed, but the service's still showing status: unknown when I do juju status.
[11:47] <babbageclunk> frobware: If I ssh into the node I can see runserver.py running which seems to point to the gui charm
[11:48] <babbageclunk> But if I click through the HTTPS warnings I can get to the gui"
[11:49] <babbageclunk> Sweet, I'm in!
[11:50] <frobware> great
[11:56] <babbageclunk> So I think everything's working, other than the "unknown" status in the cli (which isn't reflected in the gui). Probably I won't worry about that.
[12:06] <voidspace> babbageclunk: yay
[12:06] <voidspace> babbageclunk: I'm going on lunch
[12:06] <voidspace> school holidays, so no school run for the next two weeks
[12:13] <babbageclunk> voidspace: cool cool, I'm going for a run to celebrate.
[13:19] <frobware> voidspace, babbageclunk: are you guys using "      maas | 2.0.0~alpha3+bzr4810-0ubuntu1 | http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
[13:19] <frobware> "
[13:23] <frobware> voidspace, babbageclunk: I see there's an alpha4 in ppa:maas/next
[13:27] <dooferlad> fwereade_: with https://github.com/juju/juju/compare/1.25...dooferlad:1.25-proxy-state-server-bug?expand=1 I am getting API authentication errors. I assume I am missing something else that I should know, but don't. Do you have time to help?
[13:31] <fwereade_> dooferlad, looking
[13:33] <fwereade_> dooferlad, AuthClient means "is this a user". would probably be a good idea if we did s/Client/User/ across most of apiserver
[13:34] <fwereade_> dooferlad, I think you want auth.AuthMachineAgent() || auth.AuthUnitAgent()
[13:35] <dooferlad> fwereade_: thanks. Will give that a go.
[13:37] <babbageclunk> frobware: yup, that's the version I'm running - sorry, had to spin up my 2.0 kvm to check
[13:38] <natefinch> fwereade_: yeah, our use of "Client" in the codebase is quite confusing at times
[13:38] <babbageclunk> frobware: do you think I should upgrade?
[13:38] <natefinch> fwereade_: we have the Client API and then a client for the Client API, but also a client for the non-Client API
[13:39] <frobware> babbageclunk: I was trying to reach your feature parity.
[13:39] <frobware> babbageclunk: ... and I'm not there yet. Hmpf.
[13:42] <fwereade_> natefinch, really? which is the, uh, non-client client?
[13:44] <natefinch> fwereade_: well, everything under api/ is a client wrapper for a facade
[13:45] <natefinch> fwereade_: where client in this context just means "consumer of the API", as in, client-server
[13:45] <natefinch> fwereade_: I guess mostly I find it confusing that we have an API facade called "Client"
[13:46] <natefinch> fwereade_: and then there's api/Client, which is the client wrapper for the Client facade
[13:47] <fwereade_> natefinch, right, got you
[13:47] <fwereade_> natefinch, if we didn't overload Client it would all make much more sense
[13:48] <natefinch> fwereade_: indeed.  Was just thinking about it with your talk of switching client to user, which makes a lot more sense... the Client facade is really the user-facing facade, and the rest are the juju-facing facades
[13:49] <voidspace> frobware: I've been using both next-proposed and experimental3 ppas
[13:50] <frobware> voidspace: going to try next-proposed
[13:51] <frobware> voidspace: I had problems with creating the admin account. not sure if that was just finger trouble.
[13:51] <voidspace> frobware: heh
[13:51] <voidspace> I would expect to
[13:51] <voidspace> or it's another new bug
[13:52] <frobware> voidspace: like I said to babbageclunk, I wanted to get to your state-of-the-maas2-world.
[13:52] <voidspace> frobware: ok
[13:53] <frobware> voidspace: I'd like to try this installation using LXD, but that may be adding yet more entropy...
[14:00] <fwereade_> natefinch, although really, the single monolithic Client facade is itself silly -- we probably ought to just explicitly separate internal/ from external/
[14:01] <natefinch> fwereade_: yeah, definitely.  maybe call them private vs public. Private is just for juju, public is for anyone who wants to write a client
[14:01] <natefinch> fwereade_: of course, if we call something a public API, we'd have to document it ;)
[14:03] <fwereade_> natefinch, that would... not be a bad thing ;)
[14:12] <voidspace> frobware: oops, didn't reply
[14:13] <voidspace> frobware: we're definitely *not* targetting container support in the first cut of MAAS 2.0 support
[14:16] <frobware> voidspace: ahh. I meant my MAAS 2.0 installation which was using LXD vs a VM.
[14:17] <mup> Bug #1563335 opened: creating hosted model: could not create state for new model: cannot create index: read tcp 127.0.0.1:37017: i/o timeout <bootstrap> <ci> <juju-core:Triaged> <https://launchpad.net/bugs/1563335>
[14:17] <voidspace> frobware: you mean MAAS 2 *in* LXD?
[14:17] <frobware> voidspace: yep.
[14:17] <voidspace> instead of KVM
[14:17] <frobware> voidspace: correct
[14:17] <voidspace> frobware: ah cool
[14:17] <voidspace> would be lighter weight than KVM
[14:17] <voidspace> that's for sure
[14:18] <voidspace> frobware: I had to blow away both MAAS 2 installs
[14:18] <voidspace> frobware: I have it reinstalled in a fresh VM and am just updating that box
[14:18] <voidspace> frobware: I've also looked over Tim's code - it's pretty threadbare but it's a start
[14:19] <voidspace> frobware: as I said in my email I don't really understand what he means by his schema versioning stuff and I'm not convinced we need it anyway
[14:37] <babbageclunk> voidspace: to look at Tim's fork of gomaasapi, should I just git clone it, or use go get?
[14:40] <natefinch> babbageclunk: if you already have gomaasapi in your GOPATH, just git remote add Tim's fork and checkout his branch. if you don't have gomaasapi yet, go-get it first
[14:40] <babbageclunk> natefinch: great, that makes sense. Thanks!
[14:41] <natefinch> babbageclunk: welcome.  It takes a little bit to understand the way to combine real-world git environments and go, but once you get it, it's not too hard.
[14:42] <babbageclunk> Yeah, that was what I was fumbling with.
[14:43] <natefinch> babbageclunk: go get is more for end-users than developers, per se.  it's useful for setting up the right paths in your GOPATH for all the dependencies, but then to actually develop, you use the backing VCS to twiddle with what branches you're looking at.  Helps a ton to have the git branch in your prompt, btw.
[14:44] <voidspace> babbageclunk: clone
[14:44] <voidspace> babbageclunk: or https://github.com/juju/gomaasapi/compare/master...howbazaar:controller-interface
[14:44] <voidspace> babbageclunk: above link if you just want to see the differences
[14:44] <voidspace> babbageclunk: actually - I fork then pull rather than clone
[14:44] <babbageclunk> natefinch: Awesome, thanks
[14:45] <babbageclunk> voidspace: Yeah, that makes sense too, given that I'm expecting to do work on it,
[14:45] <voidspace> babbageclunk: what I actually do is fork gomaasapi, add howbazaar as a remote
[14:45] <voidspace> babbageclunk: and then I can checkout his branch or merge it into mine
[14:45] <natefinch> yeah, forking the original, then git remote add your fork to $GOPATH/github.com/juju/gomaasapi
[14:46] <natefinch> er $GOPATH/src of course
[14:46] <frobware> voidspace, babbageclunk: so this time (alpha3) I managed to get into a state where I have no cluster to edit... Hmpf.
[14:47] <voidspace> frobware: cool
[14:47] <voidspace> I'm running alpha3 too
[14:49] <voidspace> enlisted a node, now attempting to commission
[14:49] <voidspace> looks like it's working rather than trying to enlist again (the old bug)
[14:50] <mup> Bug #1563364 opened: UniterSuite.TestUniterSteadyStateUpgradeForce fails <ci> <intermittent-failure> <test-failure> <juju-core:Incomplete> <juju-core embedded-gui:New> <https://launchpad.net/bugs/1563364>
[14:50] <voidspace> hmmm... not proven yet - it seems to have stalled
[14:51] <voidspace> nope, done
[14:51] <voidspace> *great*
[14:51]  * babbageclunk highfives voidspace
[14:51] <voidspace> hah :-)
[14:51] <voidspace> o/
[14:51] <voidspace> o/\o
[14:55] <babbageclunk> voidspace: sorry to leave you hanging! Should have been watching more closely.
[14:55] <voidspace> hah
[14:55] <voidspace> no worries
[14:55] <babbageclunk> next time
[15:05] <mup> Bug #1563364 changed: UniterSuite.TestUniterSteadyStateUpgradeForce fails <ci> <intermittent-failure> <test-failure> <juju-core:Incomplete> <juju-core embedded-gui:New> <https://launchpad.net/bugs/1563364>
[15:08] <mup> Bug #1563364 opened: UniterSuite.TestUniterSteadyStateUpgradeForce fails <ci> <intermittent-failure> <test-failure> <juju-core:Incomplete> <juju-core embedded-gui:New> <https://launchpad.net/bugs/1563364>
[15:08] <mup> Bug #1563373 opened: bootstrap connection timed out <bootstrap> <ci> <juju-core:Triaged> <https://launchpad.net/bugs/1563373>
[15:08] <mup> Bug #1563380 opened: addresses for [] not found <ci> <deploy> <intermittent-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1563380>
[15:17] <mup> Bug #1563373 changed: bootstrap connection timed out <bootstrap> <ci> <juju-core:Triaged> <https://launchpad.net/bugs/1563373>
[15:17] <mup> Bug #1563380 changed: addresses for [] not found <ci> <deploy> <intermittent-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1563380>
[15:20] <mup> Bug #1563373 opened: bootstrap connection timed out <bootstrap> <ci> <juju-core:Triaged> <https://launchpad.net/bugs/1563373>
[15:20] <mup> Bug #1563380 opened: addresses for [] not found <ci> <deploy> <intermittent-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1563380>
[15:20] <mup> Bug #1563384 opened: could not exit restoring status: connection refused <backup-restore> <ci> <juju-core:Incomplete> <juju-core drop-maas-1.8-support-from-juju2:Triaged> <https://launchpad.net/bugs/1563384>
[15:26] <frobware> voidspace: did the drop-1.8 branch eventually happen?
[15:33] <voidspace> frobware: nope, need(ed?) a blessed master to get a blessed run on drop-1.8
[15:34] <voidspace> still no bless on master
[15:34] <katco> natefinch: ericsnow: hey, we can move the standup earlier for the next few weeks. what time works for you two?
[15:35] <mup> Bug #1563384 changed: could not exit restoring status: connection refused <backup-restore> <ci> <juju-core:Incomplete> <juju-core drop-maas-1.8-support-from-juju2:Triaged> <https://launchpad.net/bugs/1563384>
[15:35] <ericsnow> katco: whenever (FWIW, I liked having it at the start of my day
[15:35] <ericsnow> )
[15:36] <katco> ericsnow: is the old time ok?
[15:37] <natefinch> katco: we could do it an hour later...that way ericsnow doesn't have to start at 8 if he doesn't want to
[15:37] <katco> natefinch: ericsnow: completely up to him
[15:37] <ericsnow> katco: I'm fine either way
[15:38] <katco> ericsnow: natefinch: old time it is :)
[15:38] <katco> ericsnow: natefinch: do you two mind if we do a quick standup now to catch me up?
[15:38] <mup> Bug #1563384 opened: could not exit restoring status: connection refused <backup-restore> <ci> <juju-core:Incomplete> <juju-core drop-maas-1.8-support-from-juju2:Triaged> <https://launchpad.net/bugs/1563384>
[15:38] <ericsnow> katco: sounds good
[15:38] <natefinch> katco: sure, I was going to suggest that, actually
[15:50] <mup> Bug #1563400 opened: TestOneWorkerStartWhenStopping fails <ci> <intermittent-failure> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1563400>
[16:11] <mup> Bug #1563418 opened: TestModelDestroy fails <ci> <intermittent-failure> <test-failure> <juju-core:Incomplete> <juju-core drop-maas-1.8-support-from-juju2:Triaged> <https://launchpad.net/bugs/1563418>
[16:23] <natefinch> gah, somehow github reviews got set to wrapping at 60 characters on my screen... no idea how to fix it, but it goes away if I use incognito :/
[16:23] <natefinch> ahh... it was the sourcegraph plugin...
[16:31] <babbageclunk> voidspace: I'm reading through your and Tim's changes to gomaasapi, trying to understand what's going on there and trying to see how that would be used in the juju maas provider.
[16:31] <frobware> voidspace, babbageclunk: I can enlist, commission and deploy with alpha3 MAAS 2.0
[16:32] <babbageclunk> voidspace: also trying to match that up with the MAAS api docs so I can get a feel for it. Any other things I should be looking at?
[16:48] <katco> ericsnow: ping
[16:48] <ericsnow> katco: pong
[16:49] <katco> ericsnow: when you reach a stopping point, would you mind swinging onto 1560201 ?
[16:49] <katco> bug 1560201
[16:49] <mup> Bug #1560201: The Client.WatchAll API command never responds when the model has no machines <juju-release-support> <landscape> <juju-core:Triaged> <https://launchpad.net/bugs/1560201>
[16:49] <ericsnow> katco: k
[16:50] <katco> ericsnow: ty... critical priority =/
[17:11] <mup> Bug #1502158 changed: When HP DNS/service calls fail, juju could retry <ci> <openstack-provider> <ui> <juju-core:Won't Fix> <https://launchpad.net/bugs/1502158>
[17:42] <mup> Bug #1184457 changed: Stores user configuration outside of $XDG_CONFIG_HOME <apport-bug> <feature> <i386> <raring> <juju-core:Fix Released> <juju-core (Ubuntu):Fix Released> <https://launchpad.net/bugs/1184457>
[18:19] <arosales> hello, I wanted to do a quick sanity check for the Xenial archive in relation to juju.
[18:19] <arosales> As of today I see 3 juju packages, juju-core, juju, and juju2
[18:20] <arosales> juju-core and juju both are pointing at 1.25.0-0ubuntu3, and juju2 pointing at 2.0-beta3-0ubuntu1~16.04.2~juju1
[18:21] <arosales> at least on the s390 arch, thus for folks looking to install juju 2.0 on s390x in Xenial I am going to recommending to "sudo apt-get install juju2"
[18:22] <arosales> will this instruction change to "sudo apt-get install juju" for the 16.04 release?
[18:22] <natefinch> sinzui: ^ ?
[18:26] <natefinch> arosales: IIRC, 1.25 will stick with juju-core and 2.x will be juju... but I'm far from an authority on it.
[18:26] <katco> arosales: sinzui is definitely an authority on this. alexisb may also have some answers
[18:26] <arosales> natefinch: ok, and sounds like juju2 may just point at juju
[18:27] <arosales> that make sense
[18:27] <arosales> katco: ack
[18:27] <natefinch> arosales: that's my understanding
[18:27] <arosales> natefinch: ok, I'll run with that for now.
[18:27] <arosales> thanks katco and natefinch
[18:29] <rick_h_> arosales: we're working with the folks on this currently
[18:29] <rick_h_> arosales: juju will be the package everyone is to use and apt-get install to get juju
[18:30] <rick_h_> arosales: the others will be tweaked to point in ways to make sure the upgrade/etc works properly
[18:32] <arosales> rick_h_: and that the plan for 16.04 I take it, but today if folks want juju 2.0 from the archive they need to apt-get install juju2
[18:33] <rick_h_> arosales: right, so your question is "will apt-get install juju2 move to apt-get install juju" and the answer is yes
[18:34] <arosales> rick_h_: ok thanks
[18:54] <mup> Bug #1528932 changed: No images error when deploying services <2.0-count> <ci> <juju-core:Fix Released> <juju-core structured-metadata:Fix Released by axwalk> <https://launchpad.net/bugs/1528932>
[18:54] <mup> Bug #1531878 changed: TestBootstrapImage fails on i386 and ppc64el <2.0-count> <i386> <ppc64el> <test-failure> <unit-tests> <juju-core:Fix Released> <juju-core structured-metadata:Fix Released by axwalk> <https://launchpad.net/bugs/1531878>
[19:03] <natefinch> katco: https://golang.org/doc/go1.4#canonicalimports
[19:03] <natefinch> katco: (re: the comment on the package declaration)
[19:04] <katco> natefinch: ahhhh ok... thanks, i actually hadn't run into that in the wild yet
[19:05] <natefinch> katco: took me forever to figure out how to google for that... I remembered it being added, but not what it was called or when it was added
[19:05] <katco> natefinch: yeah. have you seen that used anywhere else?
[19:07] <natefinch> katco: not many places.  Most people are happy just to host on github.  Not sure how many people use gopkg.in or host their own redirector for their go code
[19:07] <katco> natefinch: my guess was they added that for some internal google thing
[19:09] <natefinch> katco: well, it was a kind of a pain in the butt if you *do* use gopkg.in and someone just go-gets the code from the github URL, it will be all wonky, because the root code will be under GOPATH/src/github.com/ but all the subfolders will be under gopkg.in/ because the imports all say gopkg.in
[19:30] <mup> Bug #1537152 changed: Can't re-create a model <juju-release-support> <juju-core:Triaged> <https://launchpad.net/bugs/1537152>
[19:40] <natefinch> ericsnow: do we let you elide the resource revisions when you publish a charm?  Wondering what the use case is for listing the latest resources for a charm are... seems like you'd almost always be getting specific revisions
[19:42] <ericsnow> natefinch: yes, you can omit the revision to use the latest one
[19:51] <natefinch> ericsnow: what is this doing? errgo.WithCausef(err, err, "")
[19:51]  * ericsnow waves hands
[19:51] <ericsnow> stuff
[19:52] <katco> ... lol
[19:52] <natefinch> this isn't the error return we're looking for
[19:52] <ericsnow> natefinch: it does what errors.Trace() does
[19:52] <ericsnow> natefinch: more or less
[19:54] <natefinch> ericsnow: I think the canonical way to do that is errgo.Mask(err, errgo.Any)
[19:54] <natefinch> ericsnow: which is also terrible, but slightly less terrible, IMO
[19:54]  * thumper likes trace
[19:54] <natefinch> thumper: +1
[19:55] <natefinch> honestly, trace is the only thing I really like about the errors packages... and even that, I'm sorta meh on
[20:00] <mup> Bug #1541393 changed: apiserver/logsink.log gets created while running unit tests <juju-core:Triaged> <https://launchpad.net/bugs/1541393>
[20:00] <mup> Bug #1543262 changed: keystone V3 support needed <openstack-provider> <uosci> <Go OpenStack Exchange:New> <juju-core:Fix Released> <https://launchpad.net/bugs/1543262>
[20:01] <natefinch> gah, it kills me that we pass around charm.URL as a pointer everywhere... why do we do that?  It's 5 strings and an int.  Just means we have to worry about nil pointers and modifying the caller's data, etc.
[20:07] <katco> natefinch: just 1 small point of disagreement... even with value types you still have to worry about default values
[20:07] <katco> natefinch: maybe the program won't panic (maybe), but it will still do the wrong thing
[20:10] <natefinch> katco: true... but pointers really just add a whole lot of extra pain. Like in eric's code where he's taking a pointer... but then just copies the value anyway so he doesn't accidentally overwrite the caller's data.
[20:10] <ericsnow> natefinch: alas, errgo.Mask doesn't work with errgo.Cause()
[20:10] <katco> natefinch: yes, agreed on all other points. and pass by value is the right thing to do for that type
[20:10] <natefinch> ericsnow: ug
[20:11] <natefinch> ericsnow: fair enough... I kinda figured you were doing a dance to make all the location and cause bits line up, but due to little exposure to errgo, I wasn't aware of that pattern.
[20:11] <ericsnow> natefinch: hmm, perhaps it would with errgo.Any...
[20:12] <ericsnow> natefinch: yeah, errgo is still hard to grok after using it for several days
[20:33] <mup> Bug #1554042 changed: Bootstrap, destroy-controller and kill-controller all fail after a failed bootstrap <2.0-count> <destroy-controller> <juju-release-support> <juju-core:Fix Released> <juju-core admin-controller-model:Fix Released by wallyworld> <https://launchpad.net/bugs/1554042>
[20:33] <mup> Bug #1558612 changed: creating hosted model config: maas-agent-name is already set; this should not be set by hand <2.0-count> <bootstrap> <ci> <maas-provider> <test-failure> <juju-core:Fix Released> <juju-core admin-controller-model:Fix Released by wallyworld> <https://launchpad.net/bugs/1558612>
[20:33] <mup> Bug #1558678 changed: manual bootstrap: PrepareForCreateEnvironment not implemented <2.0-count> <bootstrap> <ci> <manual-provider> <regression> <juju-core:Fix Released by axwalk> <juju-core admin-controller-model:Fix Released by axwalk> <https://launchpad.net/bugs/1558678>
[20:45] <mup> Bug #1557633 changed: status has duplicate entries for relationships <2.0-count> <juju-release-support> <juju-core:Fix Released by hduran-8> <https://launchpad.net/bugs/1557633>
[20:51] <mup> Bug #1557633 opened: status has duplicate entries for relationships <2.0-count> <juju-release-support> <juju-core:Fix Released by hduran-8> <https://launchpad.net/bugs/1557633>
[21:03] <mup> Bug #1557633 changed: status has duplicate entries for relationships <2.0-count> <juju-release-support> <juju-core:Fix Released by hduran-8> <https://launchpad.net/bugs/1557633>
[21:03] <mup> Bug #1559131 changed: unable to add-credential for maas <2.0-count> <conjure> <juju-release-support> <juju-core:Fix Released> <juju-core admin-controller-model:Fix Released by wallyworld> <https://launchpad.net/bugs/1559131>
[22:15] <mup> Bug #1563576 opened: juju 2 beta3 can't bootstrap to lcy02 <landscape> <juju-core:New> <https://launchpad.net/bugs/1563576>
[23:12] <davecheney> wow, the leankit UI really dsicourages you from commenting on cards
[23:12] <davecheney> add comment, click close, comemnt gone
[23:12] <davecheney> makr card blocked, close card, card not blocked
[23:13] <davecheney> to add a comment you have to go to the comment screen, add comment, click "add"
[23:13] <davecheney> THEN you have to go to the main card screen and click save
[23:13] <davecheney> don't do all those steps
[23:13] <davecheney> cmment is discarded
[23:13] <davecheney> yay
[23:28] <mup> Bug #1563585 opened: juju destroy-controller fails on existing controller after upgrade to Beta3 - ERROR getting controller environ: controller-uuid: expected string, got nothing <oil> <juju-core:New> <https://launchpad.net/bugs/1563585>
[23:36] <axw> ericsnow: assuming you fixed RB, did you just delete leftover stuff in /tmp? do other people have access to do that, in case you're away/unavailable?
[23:37] <ericsnow> axw: yeah, I just deleted all the /tmp/reviewboard.* directories (which hold temp diffs)
[23:37] <ericsnow> axw: anyone with access to the juju-ci4 environment can do it
[23:38] <axw> ericsnow: ok, cool, thanks
[23:38] <ericsnow> axw: np