[01:50] babbageclunk: here's that forward port of 2.7 https://github.com/juju/juju/pull/10945 [02:22] wallyworld: oops - looking [02:24] wallyworld: approved [02:32] ty [03:00] quick review for a test fix backport: https://github.com/juju/juju/pull/10946 [03:04] is github shite for anyone else? [03:04] yeah, pretty slow at the moment [03:05] slow af, also 500 errors [03:05] haven't seen those [03:05] i can't really access it [03:05] uh oh, failures in gating tests [03:06] for 2.7 though i think? [03:13] oh right - are we not worrying about that? [03:15] well, hmmm. i would like to think we've made fixes moving forward and we won't necessariy backport every fix. but right now we'd not expect any or much divergence [03:16] so any failure now could or will probably affect develop also [03:16] I'll see whether there have been any changes for the persistent-storage test in develop [03:23] nope [03:52] hpidcock: another easy review? https://github.com/juju/juju/pull/10946 [03:52] babbageclunk: sure [03:53] i should have called dibs [03:53] you snost, you lost [03:55] babbageclunk: doneski [03:56] hpidcock: merci beaucoup! [05:01] babbageclunk: +1 on your pr [05:01] thanks [08:22] Need a tick on 0-conflict forward merge. Brings forward babbageclunk's test fix: https://github.com/juju/juju/pull/10948 [08:23] stickupkid: Morning. https://github.com/juju/juju/pull/10948. [08:24] manadart, done [08:24] stickupkid: Ta. [09:23] stickupkid: Another one. https://github.com/CanonicalLtd/juju-qa-jenkins/pull/326 [09:25] morning manadart stickupkid i might need a look at this https://github.com/juju/description/pull/66 and this https://github.com/juju/juju/pull/10943 [09:25] but timewise not important, as they are not ci [09:31] nammn_de1: OK. [10:56] manadart stickupkid ci fix https://github.com/juju/juju/pull/10949 [10:56] small one [10:58] nammn_de1, i think juju is wrong here, I think maas, should have a default region [10:58] stickupkid: you mean juju should check the endpoint of maas during interactive adding? [11:08] nammn_de1 stickupkid: MAAS doesn't have regions in the Juju sense. A MAAS region controller is the cloud (endpoint). The default region is "". A MAAS Rack controller is an availability zone. [11:08] nammn_de1, approved, let's improve this test - OR we can move it to the integration tests [11:08] nammn_de1, manadart it does have a region in terms of a "client-cloud-region" [11:09] manadart, i.e. "default" is just the only one... [12:53] stickupkid: Since you reviewed the first one :) https://github.com/CanonicalLtd/juju-qa-jenkins/pull/327 [12:55] stickupkid: Hold up. I will add something to that patch. === Beret- is now known as Beret [15:50] stickupkid: https://github.com/juju/juju/pull/10951 [15:52] manadart, does it? [15:52] manadart, when i use juju switch with no argument it works, is this without a bootstrap? [15:54] ah, yes, that's right [15:54] * manadart nods. [16:29] backport to make it pass 2.7 as well https://github.com/juju/juju/pull/10952 [17:18] anyone pointers to make the `integration caas test ` run locally? Im trying it with `python3 ./assess caas_deploy_charms --caas-provider="microk8s"` [22:27] hi all, i have an issue i wanted to ask about before raising a bug, [22:27] ive deployed k8s using the ost provider [22:27] kubernetes-master says it has port 6443/tcp open [22:27] yet none of the security groups have that port open [22:28] is this a know issue? am i missing something? [22:28] ill raise a bug tomorrow with more data [23:52] dosaboy: have you exposed kubernetes-master?