[00:26] <wallyworld> thumper: whenever.... https://github.com/juju/juju/pull/11668
[01:29]  * thumper looks
[01:29]  * thumper looks briefly, and decides to look in more detail loater
[08:21] <Chipaca> 'juju status' (with 2.7.6 installed from snap) freezes apparently forever, is there a trick to it?
[08:23] <stickupkid> Chipaca, that normally happens if it can't communicate with the controller
[08:24] <stickupkid> Chipaca, there are other times when this can happen also as well, but that would be where I'd look first
[08:25] <Chipaca> stickupkid: it's just a local thing talking to an lxd, does that make a difference?
[08:25] <stickupkid> Chipaca, same scenario. What does `lxc list` say
[08:27] <Chipaca> stickupkid: so, this started happening yesterday, and as this is only used by me for testing stuff, i purged juju and lxd and reinstalled; 'lxc list' lists nothing, but 'juju bootsrap localhost overlord' tells me 'ERROR controller "overlord" already exists'
[08:27]  * Chipaca is probably breaking all kinds of stuff in his ignorance
[08:28] <stickupkid> Chipaca, so you don't have a controller, juju thinks there still is one. You have two options... clean up the ./local/share/juju yaml files or run `juju controllers --format=json | jq -r ".controllers | keys[]" | xargs -I% juju kill-controller -y -t 0 %`
[08:29] <stickupkid> it assumes you have `jq` installed.
[08:29] <Chipaca> why would the juju snap keep state outside of ~/snap :-/
[08:29] <Chipaca> sigh
[08:29] <stickupkid> --classic
[08:30] <stickupkid> Chipaca, we don't support confinement yet, we do have it on our roadmap... priorities I guess ;-)
[08:30] <Chipaca> i know, but you're just making harder for yourselves :)
[08:30] <Chipaca> anyway, thanks, that's exactly the problem
[08:30] <Chipaca> i'll nuke that and start afresh \o/
[08:31] <Chipaca> stickupkid: thanks!
[08:32] <wallyworld> stickupkid: juju unregister
[08:32] <wallyworld> will get rid of an orphaned controller entry
[08:32] <wallyworld> no direct editing of controllers.yaml needed
[08:32] <stickupkid> wallyworld, haha, knew there was another command
[08:33] <Chipaca> FWIW the jq pipeline didn't work so I went for removing ~/.local/share/juju
[08:33] <Chipaca> Unable to open API: open connection timed out
[08:33] <Chipaca> WARNING unknown config field "lxd-snap-channel"
[08:33] <Chipaca> ERROR getting controller environ: getting environ using bootstrap config from client store: Get https://10.160.185.1:8443/1.0: Unable to connect to: 10.160.185.1:8443
[08:33] <Chipaca> ~
[08:34] <stickupkid> achilleasa, this is new --> WARNING unknown config field "lxd-snap-channel" - when trying to remove a controller
[08:44] <achilleasa> stickupkid: that's a side-effect of how we access these settings in the workers. TLDR: we pop them off the map when accessed and complain about remaining entries. We do that here (https://github.com/juju/juju/blob/develop/worker/provisioner/container_initialisation.go#L207) for this field but this (https://github.com/juju/juju/blob/develop/container/lxd/manager.go#L78) doesn't hence the warning.
[08:45] <achilleasa> we could add a dummy pop in the latter file to silence the warning but I didn't add it as part of my commit because it looked weird. We can do that as a drive-by fix in any future PR
[08:59] <stickupkid> manadart, ping
[09:00] <manadart> stickupkid: Pong; just starting a call.
[09:00] <stickupkid> manadart, ping when you're free
[10:38] <manadart> stickupkid: I'm in Daily.
[12:38] <Eryn_1983_FL> hey guys
[12:38] <achilleasa> manadart: what is the current status on spaces and manual machines?
[12:38] <Eryn_1983_FL> whats the default username/password for maas and juju?
[12:38] <Eryn_1983_FL> for ssh
[12:38] <Eryn_1983_FL> im locked out atm
[12:40] <manadart> achilleasa: Currently unsupported; on the this cycle of work to enable. It just requires population of subnets from the machine NICs.
[12:51] <Eryn_1983_FL> manadart:  if i got into rescue mode can i get to a console?
[12:54] <manadart> Eryn_1983_FL: There's no default. Juju sets up it's own key in authorized_keys, which allows `juju ssh <machine-id>`.
[12:55] <Eryn_1983_FL> i dont has ssh to juju
[12:55] <manadart> Or `juju ssh <unit>` for that matter.
[12:56] <manadart> Eryn_1983_FL: You have no client connectivity to your Juju controller?
[12:56] <Eryn_1983_FL> i got the web gui
[12:59] <Eryn_1983_FL> just dont understand why my keys are not working
[13:29] <Eryn_1983_FL> time to reinstall again
[13:35] <achilleasa> quick CR https://github.com/juju/utils/pull/312 anyone? needed to fix the broken tests on develop
[14:35] <stickupkid> manadart, https://bugs.launchpad.net/juju/+bug/1882097
[14:35] <mup> Bug #1882097: Needless brute forcing with finding AZ in space topology in the provisioner task <juju:Triaged> <https://launchpad.net/bugs/1882097>
[14:40] <manadart> stickupkid: výborne
[15:25] <achilleasa> Can someone review and run the "straightforward" QA steps for https://github.com/juju/juju/pull/11670?
[15:44] <stickupkid> achilleasa, I'm stealling your PR for now (sorry for the noise)
[15:47] <achilleasa> no worries. I want to force-push a fix for one of the tests. Let me know when you need a new !!build!! in there ;-)
[15:51] <stickupkid> achilleasa, do it when ever I'm breaking stuff atm
[19:16] <pmatulis> has something changed in 2.8 that may affect deploying bundles? seems slower going through all bundle lines
[19:20] <pmatulis> really slower
[21:18] <thumper> pmatulis: yes, the multiwatcher code was refactored, and it does slightly more now
[21:18] <thumper> pmatulis: I'm currently looking into it to see what can be done
[21:19] <thumper> this is the basis of a watcher that bundle deploys use
[22:44] <pmatulis> thumper, ok thanks. what else does it do? more validation?
[23:00] <thumper> pmatulis: there shouldn't be a measurable difference between 2.7 and 2.8. If there is, we need to work out why
[23:00] <thumper> pmatulis: if you were able to show how different it is, that would be very helpful
[23:00] <thumper> https://github.com/juju/collections/pull/4
[23:08] <pmatulis> thumper, ok, will do