15:20:16 #startmeeting openstack_ansible_meeting 15:20:16 Meeting started Tue Jul 19 15:20:16 2022 UTC and is due to finish in 60 minutes. The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:20:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:20:16 The meeting name has been set to 'openstack_ansible_meeting' 15:20:38 #topic office hours 15:20:43 sorry, skipping rollcall 15:23:04 So, I saw that Rocky Linux 9 has finally released :) 15:24:14 another news, that are not that great, is that ansible-croe2.13 has valid bug, so I'd discourage anybody from using it, as it simply ignores package pinning. And while for some cases you will fail, in others it can silently do wrong thing 15:24:23 *ansible-core 15:24:53 https://github.com/ansible/ansible/issues/77969 15:24:57 for logs :D 15:25:04 Yes, thanks! 15:25:23 #link https://github.com/ansible/ansible/issues/77969 15:25:24 :D 15:26:02 I was just checking backports to Xena, and at very least horizon seems to be failing for bullseye pretty consistent, so I assume there's some valid issue in there 15:29:33 And i've noticed that centos fails intermittently a lot especially on stable branches 15:31:35 anyone noticed any change in the cpu_allocation_ratio .. in one cluster which is on 24.3.0 , cpu_allocation_ratio is at 4.0, but it refuses to go above the physical threads .. giving There was a conflict when trying to complete your request. Unable to allocate inventory: Unable to create allocation for 'VCPU' on resource provider 'UUID '. The 15:31:35 requested amount would exceed the capacity. 15:36:57 admin1: maybe You have orphaned resource allocations in placement? I've seen it many times 15:37:17 sean from openstack-nova just replied it could be a mariadb bug 15:37:41 " admin1: yep that version is apprently broken and its fixed in 10.6.8 i belive" 15:37:44 doh ! 15:38:18 ouh 15:38:28 https://lists.openstack.org/pipermail/openstack-discuss/2022-July/029536.html 15:39:26 spatel did a mariadb upgrade i think outside of the playbooks 15:39:51 i try to stick to the playbooks to ensure i don't have any unicorn deployments 15:40:20 I bet we backported mariadb bump recently but haven't released yet 15:40:26 as waiting for other backports to land 15:40:50 as eventually there're bunch of CVEs that's been released/covered recently 15:41:13 and mariadb is always a powder barrel 15:41:18 admin1 no, i always stick to OSA version of db 15:41:40 hopefully that #tmp db fix also comes in 15:41:40 anyway, I don't have any more updates. 15:42:01 I don't think we have backported it.... 15:42:06 is there a cherry pick on the mysql i can apply 15:42:15 But internally we applied 2 overrides to make it work 15:42:30 so it's quite easy to get it 15:42:41 just apt upgrade to the new version ? 15:43:07 that won't work :) 15:43:31 oh, well, indeed we backported tmp fix 15:43:57 https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/847435 15:45:20 thanks 15:46:22 #topic bug triage 15:46:31 I realized we have couple of new bugs 15:46:42 #link https://bugs.launchpad.net/openstack-ansible/+bug/1981463 15:47:25 damiandabrowski: you did quite a lot of work regarding pooling, and I'm not sure we included it in Xena, did we? 15:47:47 * noonedeadpunk meories gets shorter and shorter with age 15:47:51 *memories 15:48:40 so maybe you can take a look at that, as sounds like smth we have already fighten with? 15:53:49 also 15:53:52 #link https://bugs.launchpad.net/openstack-ansible/+bug/1980226 15:54:07 but I think this one is just misconfigured openstack_user_config I guess 15:54:28 I missed it for quite a while... 15:54:40 Will answer it till EOD 15:55:27 #endmeeting