[01:30] <wallyworld> hpidcock: small 2.8 fix for the azure cpc mirrors issue https://github.com/juju/juju/pull/12236
[01:31] <hpidcock> Looking
[01:34] <hpidcock> wallyworld: LGTM
[01:34] <wallyworld> ta
[03:33] <wallyworld> hpidcock: here's the 2.8 merge into develop https://github.com/juju/juju/pull/12237
[03:33] <hpidcock> wallyworld: looking
[03:34] <hpidcock> wallyworld: any conflicts that needed manual merging?
[03:35] <wallyworld> just a couple of small one line issues with DefaultSeries() moving packages
[03:35] <hpidcock> alright
[04:16] <kelvinliu_> wallyworld: small 2.9 fix for legacy disable-name-prefix https://github.com/juju/juju/pull/12238 +1 plz
[04:17] <wallyworld> sure
[04:17] <wallyworld> kelvinliu_: no test fallout?
[04:18] <kelvinliu_> seems we updated all tests to support new labels/annotations
[04:18] <wallyworld> ah yes
[04:18] <kelvinliu_> no legacy stuff is tested
[04:18] <wallyworld> lgtm
[04:19] <kelvinliu_> ty
=== tamas_erdei is now known as terdei
[09:04] <Hybrid512> Hi
[09:04] <Hybrid512> I just created this bug report : https://bugs.launchpad.net/juju/+bug/1902496
[09:04] <mup> Bug #1902496: Juju disrupting deployments when upgrading controller <juju:New> <https://launchpad.net/bugs/1902496>
[09:05] <Hybrid512> very annoying stuff ... not the one you want to have in a critical environment
[09:10] <manadart> Hybrid512: Thanks for the bug report; we'll take a look.
=== mup_ is now known as mup
[12:27] <stickupkid> manadart, updated the PR https://github.com/juju/juju/pull/12196
[14:59] <stickupkid> hml, https://github.com/juju/juju/pull/12243
[15:37] <hml> stickupkid: jq error on cleanup
[15:37] <stickupkid> which was?
[15:37] <hml> in the pr
[15:43] <hml> stickupkid: let me run again… odd message in clean up, could have been me
[15:43] <stickupkid> we shouldn't see the error tbh
[16:01] <hml> stickupkid: no error this time
[16:01] <stickupkid> nice nice
[16:04] <hml> stickupkid: approved
[22:57] <TuesdayYet> Hi all. When using multi-gateways; how do I define a default route overall to my deployed containers with multiple interfaces when deploying from maas?
[22:58] <TuesdayYet> (I have asked in #maas with no responses) - wondering if anyone has had any experience over here?
[23:03] <wallyworld> do you have a link to the maas post? i can poke someone to look at it. i suspect they'll need to know a little more detail about what you are deploying, what charms, etc
[23:04] <TuesdayYet> wallyworld: does this help? https://discourse.juju.is/t/specify-gateway-for-multiple-spaces/513
[23:05] <wallyworld> oh wow, that's an old post
[23:05] <TuesdayYet> It's an openstack deployment. Unfortunately, when defining public spaces and management spaces, the routes are placed in an order that stops internet access :(  Yeah, it's old, so i'm hoping for a solution, and yet I've been googling my little heart out to no avail.
[23:07] <wallyworld> i'll poke the right people and get an answer for you. a lot has happened in juju since then with space support, and also things like run scripts that can be passed in via cloud init (to maybe manually set up a route or something). i'm not so sure on maas. but i'll ping someone in the next day or so
[23:09] <TuesdayYet> Thanks for this. I'll check back with you. I doubt I can be the only person with this issue - so I assume i'm missing something obvious
[23:48] <wallyworld> kelvinliu_: no rush, did this PR yesterday when debugging a model upgrade bug https://github.com/juju/juju/pull/12239
[23:48] <kelvinliu_> looking
[23:56] <kelvinliu_> wallyworld: ho?
[23:56] <wallyworld> sure