15:00:14 #startmeeting openstack_ansible_meeting 15:00:14 Meeting started Tue Oct 4 15:00:14 2022 UTC and is due to finish in 60 minutes. The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:14 The meeting name has been set to 'openstack_ansible_meeting' 15:00:19 #topic rollcall 15:00:30 o/ 15:00:39 o/ double booked for this but will have it up on the screen :) g'day folks 15:01:01 thanks! 15:01:58 o/ hello 15:05:07 #topic office hours 15:05:27 So first thing - Xena is broken due to cloudsmith dropped erlang version we were using 15:06:15 This also blocking Xena as upgrade jobs are also broken 15:06:20 *Yoga 15:06:50 To unblock we need this https://review.opendev.org/c/openstack/openstack-ansible-rabbitmq_server/+/860208 15:07:09 But also, what's more important, I'm not sure if we should continue consuming cloudsmith.... 15:07:34 I really can't follow their updates and don't really understand policies either 15:07:51 As they've dropped completely erlang 23 now but some 22 are still there 15:08:27 But what's worse - I'm not sure what alternatives are 15:10:08 Next thing - https://review.opendev.org/q/topic:osa%252Ftest_volumes seems passing and functional now. So feel free to review that 15:11:44 Question about mariadb version bump: https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/858555 - should we backport it? As sounds like it's worthy thing to backport considering it will allow to sync debian and redhat versions 15:13:51 I'm running 10.6.9 for quite some time now (since I've found that fix for not backuping redo log, if you remember) and it seems fine (if that helps in any way). 15:15:27 yep, that's quite useful info I'd say 15:16:04 sounds reasonable to backport - though it's unusual 15:17:43 yeah, we should add release note when backporting 15:19:31 then this is lingering around https://review.opendev.org/c/openstack/openstack-ansible-rabbitmq_server/+/855985 15:20:14 Yeah. I think we need to drop debian-11 from there 15:20:44 Dmitriy Rabotyagov proposed openstack/openstack-ansible-rabbitmq_server master: Update rabbitmq to 3.10.7-1 https://review.opendev.org/c/openstack/openstack-ansible-rabbitmq_server/+/855985 15:21:41 I kind of wonder when next long-term mariadb will be... 15:22:07 As I feel somehow uncomfortable with 10.6 when having 10.10 as current one 15:23:23 I'm already unsure if there will be any LTS release in the future.... 15:24:51 Ah, found, `A new long-term support MariaDB Server version will be announced for General Availability approximately once every two years` 15:25:10 10.6 was released 6 Jul 2021. So one more year to wait.... 15:26:01 I hope there will be upgrade path lol 15:27:41 btw, ansible 2.13 now fails on Rocky 9 somehow 15:29:56 oh hardening role 15:30:44 it also somewhat fails on debian git-core isntallation which is super weird 15:31:37 rocky is quite consistant on where it fail: https://zuul.opendev.org/t/openstack/build/6a530b60ab1342baae9adac39368d796/log/job-output.txt#7921 15:33:57 oh my https://opendev.org/openstack/ansible-hardening/src/branch/master/library/get_users 15:34:17 lol, TIL about that 15:35:56 oh i was just going to say i bet thats a python3 problem 15:36:00 how that works for other distros 15:36:10 $massive_hack ? 15:36:15 yeah.... 15:36:34 Should we move that to plugins? 15:37:10 As hardening used to be quite "stadalone" thing 15:37:25 I'm not even sure we used config_tmeplate there 15:37:31 no 15:37:45 i dunno really - theres not really any reuse of that module anywhere 15:38:01 so moving it to plugins is not totally necessary 15:38:12 And I can't imagine possible usecase elsewhere 15:38:13 🤔 15:38:14 maybe better to fix it in place first 15:38:22 agree 15:40:01 does even modules need shebang? 15:40:35 how does all stuff in https://opendev.org/openstack/openstack-ansible-plugins/src/branch/master/plugins/modules work lol 15:41:29 or it's also $massive_hack.... 15:41:53 ansible docs for writing modules use shebang.. but not clear if needed 15:43:00 shouldn't they be using ansible_python_interpreter.... 15:43:23 Oh, and for rocky we don't have discovered_python_interpreter, that's why it falls back to shebang I guess 15:43:36 https://drop1.neilhanlon.me/irc/uploads/72ea47b1e577fbfc/image.png 15:44:20 from: https://docs.ansible.com/ansible/latest/dev_guide/developing_program_flow_modules.html#id14 15:45:05 I'd say should be safe to drop shebang then 15:45:11 agreed 15:46:32 Dmitriy Rabotyagov proposed openstack/ansible-hardening master: Remove sebang from get_users https://review.opendev.org/c/openstack/ansible-hardening/+/860276 15:46:47 also sounds like some ansible behaviour has changed with 2.13 regarding to shebangs 15:47:06 and they also check for discovered interpreter... 15:49:59 Dmitriy Rabotyagov proposed openstack/openstack-ansible-plugins master: Drop shebangs from ansible modules https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/860277 15:50:14 Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Bump ansible-core version to 2.13.4 https://review.opendev.org/c/openstack/openstack-ansible/+/857506 15:50:28 let's see if that helps... 15:51:34 though we should really look how to workaround non-defined discovered_python_interpreter for rocky (as we explicitly provide interpreter with env var which disables discovery) 15:53:48 in any case that's all I have for you today 16:00:08 #endmeeting