[08:48] <manadart_> achilleasa: Just gonna eat something, but I need a quick chat with you about the instance-poller worker.
[09:03] <achilleasa> manadart_: sure; ping when back
[09:07] <manadart_> achilleasa: Kickin' it in Daily.
[09:54] <bthomas> Just an FYI: First time I tried to install juju using snap I got the following error --  "Run hook connect-plug-peers of snap "juju" (run hook "connect-plug-peers": error: cannot communicate with server: timeout exceeded while waiting for response)". Snap list showed that the juju snap had not installed. On attempting to install Juju a second time it worked seemlessly. Seems like a race condition. I have not tried to debug/reproduce
[09:54] <bthomas> it. One way to reproduce it may be to stop microk8s, then start it and soon after try installing juju snap.
[10:19] <Chipaca> bthomas: #snappy may also be interested in that fwiw
[10:19] <Chipaca> i'm not there so maybe you already told them
[10:19] <Chipaca> (i'm not there because if i were i'd work on snappy stuff :-p)
[10:26] <Chipaca> jam: I think the only sane way out of this dispatch mess we've dug ourselves into is to look at the juju version, like what we did with has_app_data
[10:26] <Chipaca> jam: which means main needs to parse the juju version, and so does model (for app data)
[10:26] <Chipaca> jam: DRY would mean doing that once in main and then passing it in to model
[10:26] <Chipaca> is that worth it?
[10:29] <Chipaca> wait, wrong channel
[10:29]  * Chipaca facepalms
[10:53] <manadart_> bthomas: Can confirm. I removed/re-installed Microk8s around it, and it worked.
[10:54] <bthomas> manadart_: Hmmm. If I see it again I will try and dig a bit deeper.
[12:10] <manadart_> achilleasa: Forward merge: https://github.com/juju/juju/pull/11880
[12:10] <achilleasa> manadart_: any conflicts?
[12:10] <achilleasa> ah, nevermind
[12:11] <manadart_> achilleasa: It's mine, plus a one-liner from Ian.
[12:47] <gnuoy> When I upgrade my 2.8.1 controller to 2.8.2 it never seems to register that the upgrade has succeeded. list-controllers still reports it is on 2.8.1. show-controller reports that  controller-model-version is 2.8.2 but agent version is 2.8.1.
[12:47] <gnuoy> I am upgrading it with "juju upgrade-controller --agent-stream=devel"
[12:48] <gnuoy> My env is totally disposable fwiw
[12:48] <manadart_> gnuoy: Let me try to repro.
[12:48] <gnuoy> I am trying to reproduce a bug reported by a user who some how managed to get themselves on 2.8.2
[12:48] <gnuoy> thanks manadart_
[12:50] <gnuoy> manadart_, fwiw the machine-0.log on the controller contains a lot of:
[12:50] <gnuoy> 2020-08-05 12:45:59 ERROR juju.worker.dependency engine.go:671 "upgrader" manifold worker returned unexpected error: no matching agent binaries available
[12:54] <manadart_> gnuoy: The devel stream doesn't have them. We have not been publishing there for some time it appears. Try `--agent-stream=proposed`.
[12:55] <gnuoy> manadart_, "no upgrades available"
[12:56] <gnuoy> manadart_, I can recreate the 2.8.1 and try again with proposed
[12:56] <manadart_> gnuoy: Hmm. OK, I'll look in a mo'.
[13:08] <gnuoy> manadart_, fwiw redeploying and using `--agent-stream=proposed` resulted in the same outcome; controller-model-version at 2.8.2 but agent version at 2.8.1 and the same "no matching agent binaries available" entries in the controller log. Although I see no reference to 2.8.2 in machine-0.log at all
[13:08] <manadart_> gnuoy: OK, OTP presently, but I'll suss it our immediately after.
[13:48] <gnuoy> Is it expected that an upgrade to Juju 2.8.2 will trigger a charms install hook ? That appears to be mcayland observed yesterday (and it highlighted a bug in the nova-cloud-controller charm). I cannot reproduce that behaviour when upgrading to 2.8.1. I haven't managed to upgrade to 2.8.2 yet. Upgrading to 2.8.1 from <2.8 causes relation hooks to fire but I haven't seen the install hook fire.
[14:15] <pmatulis> gnuoy, after controller upgrade try 'juju controllers --refresh'
[14:16] <manadart_> achilleasa: See comment regarding install hook from gnuoy ^
[14:17] <gnuoy> pmatulis, yeah, I was doing the refresh
[14:42] <manadart_> gnuoy: https://bugs.launchpad.net/juju/+bug/1890452
[14:42] <mup> Bug #1890452: Juju allows upgrade based on stream, but fails to find agent binaries <juju:New> <https://launchpad.net/bugs/1890452>
[14:42] <gnuoy> thanks manadart_
[15:12] <manadart_> gnuoy: The work-around to force it into action is `juju model-config agent-stream=proposed`.
[15:13] <gnuoy> ah, great, thans manadart_
[15:13] <manadart_> For the controller ^
[15:13] <gnuoy> * thanks
[15:13]  * manadart_ nods.
[17:08] <achilleasa> can I get a review on https://github.com/juju/juju/pull/11881?
[17:08] <achilleasa> hml: you might want to take a look ^ it's the next step from the PR you reviewed yest
[17:08] <hml> achilleasa:  ack
[17:14] <achilleasa> petevg: can you also do a QA and doc check (I changed the docs for the three hook tools) for ^^^
[17:15] <petevg> achilleasa: will do!