[00:15] thumper: https://github.com/juju/juju/pull/11633 [01:42] * thumper looks [05:42] https://github.com/juju/juju/pull/11635 for some more cleanup [05:43] wallyworld: I'm heading inside, you may need to get kelvinliu or tlm to approve the 2.7 merge forwards into RC branc [05:43] h [05:43] ok [05:43] almost done landing in 2.7 [05:46] was running through the 20.05 openstack install and hit the following error, which seems like maybe a charm configuration issue [05:46] Executing changes: [05:46] - upload charm cs:ceph-mon-48 for series focal [05:46] - deploy application ceph-mon on focal using cs:ceph-mon-48 [05:46] ERROR cannot deploy bundle: ceph-mon is not available on the following series: focal not supported [05:47] when I look here focal is listed a supported https://jaas.ai/ceph-mon/48 [05:47] tychicus: unless the charm declares it supports focal, you will need to use --force and hope it works regardless [05:48] hmm, interesting [05:48] maybe the bundle has some series config which conflicts [05:49] oh, what release of juju is this [05:49] checking [05:50] 2.7.1-mojave-amd64 [05:50] ah, you may need a later version. 2.7.6 is recommended [05:50] i think focal was added around that time, can't recall if it was 2.7.1 or 2.7.2 [05:51] thanks, I'll give that a whirl [05:51] if no luck let us know [05:52] Will do, thanks for the quick response [05:58] wallyworld: need me to approve ? [05:58] still waiting for 2.7 to land, then forward port [05:58] soon hopefully [06:01] FFS, another trasient failure [06:09] so I updated the client and controller to 2.7.6, but I get the same error that focal is not supported [06:12] tychicus: can you share the bundle being used and repor steps? a bug would be useful so everything is together in one spot [06:12] *repro [06:13] it maybe a set up issue or whtever, we can comment on the bug and close it if it gets resolved [06:13] https://github.com/openstack-charmers/openstack-bundles/blob/master/stable/openstack-base/bundle.yaml [06:14] juju deploy ./bundle.yaml [06:14] should the bug be filed against the charm or the bundle? [06:14] juju [06:14] https://bugs.launchpad.net/juju [06:15] bundle looks ok to me at first glance [06:16] you could try and work around it by setting the series in the bundle to bionic and see if that helps [06:18] I can give that a go, that will just tell MaaS to deploy a 18.04 machine rather than 20.04, is that correct? [06:18] yeah [06:18] might get you unstuck until it is figured out [06:19] tychicus: you definitely have focal images in your maas? [06:19] doublechecking [06:20] it does look like a juju error message though [06:21] yes indeed 20.04 is synced on MaaS [06:22] weird, no idea at this stage without digging into it [06:22] --force will work also i think [06:22] juju deploy --force [06:23] I'll give force a try and in the mean time I'll get a bug filed [06:25] ty [06:40] wallyworld: https://bugs.launchpad.net/juju/+bug/1881071 [06:40] Bug #1881071: ceph-mon-48 does not support focal [06:40] if there is anything else that you would like to see in the bug report please let me know [07:28] manadart: sorry, got a bit over zealous getting bugs in order for the rc3 release, lining up those that will be in 2.8 since we're forward porting 2.7 for rc3 [07:35] wallyworld: If we are doing RC3, I would like to back-port some performance patches: 11570, 11606 and 11608. This is a nice combo that deliver performance improvements. [07:38] manadart: just looked at those, they look fine to me for backporting [07:38] wallyworld: How soon do we need the hash? [07:38] i'm currently landing a cmr fix in 2.7, after which i have a forward port lined up to pick it and a couple of other small fixes [07:39] i was hoping to have rc3 ready for QA in a few hours but am having issues landing the 2.7 patch [07:39] timeouts etc in some full stack tests [07:39] if we can get it to QA for their SOD that would be good [07:39] wallyworld: Let me do the hack we've been using. It's `dep ensure` for the 2.7 branch that takes all the test time. [07:40] it's the tests themselves :-( [07:40] last run was some container init tests [07:40] and before that some agent ones [07:41] always happens when you need to get stuff done urgently [07:42] wallyworld: OK. [07:42] manadart: so the rc3 trigger was bug 1881021 which i diagnosed and fixed but as per email from tim, we also need to confirm that the other observations are fixed or not [07:42] Bug #1881021: inappropriate "relation-joined" for unit bounces untiter repeatedly

[07:43] i ran out of time to go and dig [08:03] manadart, did you see my updates? [08:04] manadart, https://github.com/juju/juju/pull/11631 [08:04] stickupkid: Will look in a bit. [08:04] cheers [08:10] stickupkid: here's a foward port of 2.7 into 2.8rc to pick up a few key PRs for rc3. you guys may have one or two more to land, but landing this now will ensure the diff is a bit more managale https://github.com/juju/juju/pull/11636 [08:10] ty in advance :-) [08:12] wallyworld, "##[error]state/cleanup.go:1227:54: undefined: machineId" [08:13] stickupkid: ah, missed that, one sec [08:15] stickupkid: fixed, there was obviously a variable rename in the uprade series cleanupjob and that instance was from a change added in 2.8 [08:18] wallyworld, looks good to me [08:18] tyvm [08:30] wallyworld or stickupkid: https://github.com/juju/juju/pull/11637 [08:30] wallyworld, another failure around params package https://github.com/juju/juju/pull/11636/checks?check_run_id=716013943 [08:34] is there any way to force the mysql-router to bootstrap? [08:34] MySQL Router not yet bootstrapped [08:35] manadart: lgtm [08:37] juju actions mysql-router reports [08:37] ERROR application "mysql-router" not found [08:40] tychicus: i assume mysql-router is a deployed charm for which you want to list the actions? [08:41] yeah, I thought it was part of the bundle but it looks like maybe not [08:42] juju deploy mysql-router [08:42] Located charm "cs:mysql-router-0". [08:42] Deploying charm "cs:mysql-router-0". [09:01] so it looks like there is a mysql router for a number of services [09:02] maybe these questions are better aimed at #openstack-charms [10:50] manadart, ping [10:52] stickupkid: Pong. [10:52] daily? === salmankhan1 is now known as salmankhan [16:26] manadart, at some point in the future https://github.com/juju/juju/pull/11639 [16:47] hello everyoneapologies if this has been asked before, however i've searched the net far and wide and still can't get my issue fixed.i'm trying to deploy openstack from a charm bundle (tried various revisions of openstack-base and openstack-telemetry) and juju doesn't bind the applications to network spacesi keep getting `failed to start machine [16:47] 0/lxd/0 (unable to setup network: no obvious space for container "0/lxd/0", host machine has spaces:` [22:17] wallyworld: any merge conflicts on the 2.8-rc -> 2.8 pr? [22:33] https://github.com/juju/juju/pull/11635 awaiting someone to approve it [22:34] I can take a look thumper [22:35] thanks tlm [23:48] hi guys [23:48] we keep getting ovn errors on our openstack roll out [23:48] currently we got certificates missing errors. [23:49] any ideas of whats going on..