| wallyworld | thumper: https://github.com/juju/juju/pull/11633 | 00:15 |
|---|---|---|
| * thumper looks | 01:42 | |
| thumper | https://github.com/juju/juju/pull/11635 for some more cleanup | 05:42 |
| thumper | 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 |
| thumper | h | 05:43 |
| wallyworld | ok | 05:43 |
| wallyworld | almost done landing in 2.7 | 05:43 |
| tychicus | was running through the 20.05 openstack install and hit the following error, which seems like maybe a charm configuration issue | 05:46 |
| tychicus | Executing changes: | 05:46 |
| tychicus | - upload charm cs:ceph-mon-48 for series focal | 05:46 |
| tychicus | - deploy application ceph-mon on focal using cs:ceph-mon-48 | 05:46 |
| tychicus | ERROR cannot deploy bundle: ceph-mon is not available on the following series: focal not supported | 05:46 |
| tychicus | when I look here focal is listed a supported https://jaas.ai/ceph-mon/48 | 05:47 |
| wallyworld | tychicus: unless the charm declares it supports focal, you will need to use --force and hope it works regardless | 05:47 |
| wallyworld | hmm, interesting | 05:48 |
| wallyworld | maybe the bundle has some series config which conflicts | 05:48 |
| wallyworld | oh, what release of juju is this | 05:49 |
| tychicus | checking | 05:49 |
| tychicus | 2.7.1-mojave-amd64 | 05:50 |
| wallyworld | ah, you may need a later version. 2.7.6 is recommended | 05:50 |
| wallyworld | i think focal was added around that time, can't recall if it was 2.7.1 or 2.7.2 | 05:50 |
| tychicus | thanks, I'll give that a whirl | 05:51 |
| wallyworld | if no luck let us know | 05:51 |
| tychicus | Will do, thanks for the quick response | 05:52 |
| tlm | wallyworld: need me to approve ? | 05:58 |
| wallyworld | still waiting for 2.7 to land, then forward port | 05:58 |
| wallyworld | soon hopefully | 05:58 |
| wallyworld | FFS, another trasient failure | 06:01 |
| tychicus | so I updated the client and controller to 2.7.6, but I get the same error that focal is not supported | 06:09 |
| wallyworld | 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 |
| wallyworld | *repro | 06:12 |
| wallyworld | it maybe a set up issue or whtever, we can comment on the bug and close it if it gets resolved | 06:13 |
| tychicus | https://github.com/openstack-charmers/openstack-bundles/blob/master/stable/openstack-base/bundle.yaml | 06:13 |
| tychicus | juju deploy ./bundle.yaml | 06:14 |
| tychicus | should the bug be filed against the charm or the bundle? | 06:14 |
| wallyworld | juju | 06:14 |
| wallyworld | https://bugs.launchpad.net/juju | 06:14 |
| wallyworld | bundle looks ok to me at first glance | 06:15 |
| wallyworld | you could try and work around it by setting the series in the bundle to bionic and see if that helps | 06:16 |
| tychicus | 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 |
| wallyworld | yeah | 06:18 |
| wallyworld | might get you unstuck until it is figured out | 06:18 |
| wallyworld | tychicus: you definitely have focal images in your maas? | 06:19 |
| tychicus | doublechecking | 06:19 |
| wallyworld | it does look like a juju error message though | 06:20 |
| tychicus | yes indeed 20.04 is synced on MaaS | 06:21 |
| wallyworld | weird, no idea at this stage without digging into it | 06:22 |
| wallyworld | --force will work also i think | 06:22 |
| wallyworld | juju deploy <bundle> --force | 06:22 |
| tychicus | I'll give force a try and in the mean time I'll get a bug filed | 06:23 |
| wallyworld | ty | 06:25 |
| tychicus | wallyworld: https://bugs.launchpad.net/juju/+bug/1881071 | 06:40 |
| mup | Bug #1881071: ceph-mon-48 does not support focal <juju:New> <https://launchpad.net/bugs/1881071> | 06:40 |
| tychicus | if there is anything else that you would like to see in the bug report please let me know | 06:40 |
| wallyworld | 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:28 |
| manadart | 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:35 |
| wallyworld | manadart: just looked at those, they look fine to me for backporting | 07:38 |
| manadart | wallyworld: How soon do we need the hash? | 07:38 |
| wallyworld | 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:38 |
| wallyworld | i was hoping to have rc3 ready for QA in a few hours but am having issues landing the 2.7 patch | 07:39 |
| wallyworld | timeouts etc in some full stack tests | 07:39 |
| wallyworld | if we can get it to QA for their SOD that would be good | 07:39 |
| manadart | 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:39 |
| wallyworld | it's the tests themselves :-( | 07:40 |
| wallyworld | last run was some container init tests | 07:40 |
| wallyworld | and before that some agent ones | 07:40 |
| wallyworld | always happens when you need to get stuff done urgently | 07:41 |
| manadart | wallyworld: OK. | 07:42 |
| wallyworld | 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 |
| mup | Bug #1881021: inappropriate "relation-joined" for unit bounces untiter repeatedly <cdo-qa> <cdo-release-blocker> <foundations-engine> <uniter-worker> <vsphere-provider> <juju:Fix Committed by wallyworld> <https://launchpad.net/bugs/1881021> | 07:42 |
| wallyworld | i ran out of time to go and dig | 07:43 |
| stickupkid | manadart, did you see my updates? | 08:03 |
| stickupkid | manadart, https://github.com/juju/juju/pull/11631 | 08:04 |
| manadart | stickupkid: Will look in a bit. | 08:04 |
| stickupkid | cheers | 08:04 |
| wallyworld | 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 |
| wallyworld | ty in advance :-) | 08:10 |
| stickupkid | wallyworld, "##[error]state/cleanup.go:1227:54: undefined: machineId" | 08:12 |
| wallyworld | stickupkid: ah, missed that, one sec | 08:13 |
| wallyworld | 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:15 |
| stickupkid | wallyworld, looks good to me | 08:18 |
| wallyworld | tyvm | 08:18 |
| manadart | wallyworld or stickupkid: https://github.com/juju/juju/pull/11637 | 08:30 |
| stickupkid | wallyworld, another failure around params package https://github.com/juju/juju/pull/11636/checks?check_run_id=716013943 | 08:30 |
| tychicus | is there any way to force the mysql-router to bootstrap? | 08:34 |
| tychicus | MySQL Router not yet bootstrapped | 08:34 |
| wallyworld | manadart: lgtm | 08:35 |
| tychicus | juju actions mysql-router reports | 08:37 |
| tychicus | ERROR application "mysql-router" not found | 08:37 |
| wallyworld | tychicus: i assume mysql-router is a deployed charm for which you want to list the actions? | 08:40 |
| tychicus | yeah, I thought it was part of the bundle but it looks like maybe not | 08:41 |
| tychicus | juju deploy mysql-router | 08:42 |
| tychicus | Located charm "cs:mysql-router-0". | 08:42 |
| tychicus | Deploying charm "cs:mysql-router-0". | 08:42 |
| tychicus | so it looks like there is a mysql router for a number of services | 09:01 |
| tychicus | maybe these questions are better aimed at #openstack-charms | 09:02 |
| stickupkid | manadart, ping | 10:50 |
| manadart | stickupkid: Pong. | 10:52 |
| stickupkid | daily? | 10:52 |
| === salmankhan1 is now known as salmankhan | ||
| stickupkid | manadart, at some point in the future https://github.com/juju/juju/pull/11639 | 16:26 |
| madFren | 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 |
| madFren | 0/lxd/0 (unable to setup network: no obvious space for container "0/lxd/0", host machine has spaces:` | 16:47 |
| hpidcock | wallyworld: any merge conflicts on the 2.8-rc -> 2.8 pr? | 22:17 |
| thumper | https://github.com/juju/juju/pull/11635 awaiting someone to approve it | 22:33 |
| tlm | I can take a look thumper | 22:34 |
| thumper | thanks tlm | 22:35 |
| Eryn_1983_FL | hi guys | 23:48 |
| Eryn_1983_FL | we keep getting ovn errors on our openstack roll out | 23:48 |
| Eryn_1983_FL | currently we got certificates missing errors. | 23:48 |
| Eryn_1983_FL | any ideas of whats going on.. | 23:49 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!