15:03:32 <noonedeadpunk> #startmeeting openstack_ansible_meeting
15:03:32 <opendevmeet> Meeting started Tue Oct  8 15:03:32 2024 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:03:32 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:03:32 <opendevmeet> The meeting name has been set to 'openstack_ansible_meeting'
15:03:36 <noonedeadpunk> #topic rollcall
15:03:38 <noonedeadpunk> o/
15:05:56 <jrosser> o/ hello
15:06:06 <NeilHanlon> hiya
15:06:17 <noonedeadpunk> #topic office hours
15:06:31 <noonedeadpunk> so it seem right now we do have broken upgrade jobs for 2023.1
15:06:45 <noonedeadpunk> due to missing repo mirrors I assume,
15:07:20 <noonedeadpunk> as it;s where they're failing
15:07:40 <noonedeadpunk> and I guess we have 2 ways here - either drop upgrade jobs, as 2023.1 going to unmaintained very soon
15:07:49 <noonedeadpunk> or stop using infra mirror for mariadb
15:10:41 <jrosser> is it that the mirror has not been kept up to date?
15:11:04 <noonedeadpunk> actually, thinking about that, I wonder if that's just mariadb pulled the trigger...
15:11:11 <jrosser> it just seems to stop at 10.5.9
15:12:45 <noonedeadpunk> you mean the infra one?
15:13:07 <jrosser> well i don't know - it's just a pass though proxy isnt it? with caching?
15:13:14 <noonedeadpunk> I think so, yeah
15:13:36 <jrosser> right, so same is seen here https://downloads.mariadb.com/MariaDB/
15:14:10 <jrosser> i thought i started a patch ages ago to update the location, but somehow it was not needed?
15:14:32 <noonedeadpunk> yeah
15:14:52 <noonedeadpunk> as current one was maintianing more versions or smth
15:15:48 <noonedeadpunk> but the link you supplied doesn't contain anything modern at all?
15:17:20 * noonedeadpunk already can't recall
15:18:11 <jrosser> huh everything is a magic setup script how
15:18:13 <jrosser> *now
15:18:34 <noonedeadpunk> there's https://mirror.mariadb.org/repo/ as well
15:18:41 <noonedeadpunk> but they keep only "latest"
15:20:09 <noonedeadpunk> but I think it's not what happening
15:20:17 <noonedeadpunk> I guess repo is just not browsable
15:20:59 <noonedeadpunk> or maybe 10.11 is the last release there....
15:21:55 <noonedeadpunk> yeah....
15:22:52 <noonedeadpunk> probably indeed it's time to switch then :(
15:23:15 <noonedeadpunk> I wonder how ours 11.4 patch even worked then
15:23:49 <noonedeadpunk> #link https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/922377
15:24:44 <jrosser> did they fix the TLS stuff for localhost?
15:24:53 <noonedeadpunk> um, yes, but in 11.4.4
15:24:58 <noonedeadpunk> which is not released yet
15:26:00 <noonedeadpunk> and that was your patch: https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/924354
15:26:50 <noonedeadpunk> seems it needs to be revised again
15:27:53 <noonedeadpunk> so we're just lucky to have 10.11 in there, while 10.6 just gone
15:28:58 <jrosser> urgh yes and before we didnt have to rely on any pinning because there was a repo per release
15:29:10 <noonedeadpunk> yeah
15:29:36 <noonedeadpunk> and mirror.mariadb.org also tends to maintian only last N releases, which is annoying as well
15:30:54 <noonedeadpunk> Another thing, I decided to clean-up a rabbitmq role a bit
15:31:06 <noonedeadpunk> and also look into how we're doing upgrades
15:31:29 <noonedeadpunk> with idea to finally split "rabbitmq_upgrade" with re-installing/bootstrapping cluster
15:31:46 <noonedeadpunk> to make upgrade in fact rolling
15:36:17 <noonedeadpunk> during that was able to reproduce previously reported issue, where running rabbitmq_upgrade on failing cluster was just failing
15:39:59 <opendevreview> Dmitriy Rabotyagov proposed openstack/openstack-ansible stable/2023.1: Remove upgrade jobs for 2023.1  https://review.opendev.org/c/openstack/openstack-ansible/+/931813
15:40:35 <opendevreview> Dmitriy Rabotyagov proposed openstack/openstack-ansible stable/2023.1: Bump SHAs for 2023.1  https://review.opendev.org/c/openstack/openstack-ansible/+/931742
15:49:35 <noonedeadpunk> We're coming closer to PTG and I guess we need to pick a time for that
15:50:43 <noonedeadpunk> trcky thing - I am happen to travel that specific week
15:51:19 <noonedeadpunk> But I think smth like since 16 utc should work for me....
15:58:57 <noonedeadpunk> or like Friday once I'm back :(
16:03:10 <noonedeadpunk> #endmeeting