15:01:01 <noonedeadpunk> #startmeeting openstack_ansible_meeting 15:01:01 <opendevmeet> Meeting started Tue Dec 5 15:01:01 2023 UTC and is due to finish in 60 minutes. The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:01 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:01 <opendevmeet> The meeting name has been set to 'openstack_ansible_meeting' 15:01:06 <noonedeadpunk> #topic rollcall 15:01:07 <noonedeadpunk> o/ 15:01:17 <jrosser> o/ 15:02:18 <damiandabrowski> hi! (i just got back from a vacation) 15:02:35 <NeilHanlon> o/ 15:02:46 <NeilHanlon> welcome back damiandabrowski :) hope it was a good holiday 15:04:12 <damiandabrowski> yeah thanks, finally i had some rest :D 15:05:20 <noonedeadpunk> that is really sweet :) 15:05:26 <noonedeadpunk> #topic office hours 15:05:49 <noonedeadpunk> So, I wanna re-raise one of recent bug reports, as we had chance to triage it on the production :D 15:06:09 <noonedeadpunk> #link https://bugs.launchpad.net/openstack-ansible/+bug/2038818 15:06:32 <spatel> Do you know how to delete cinder-volume services ? 15:06:39 <noonedeadpunk> My idea is not great, but well.... I was thinking, that maybe we should jsut enable all flags once rabbitmq_upgrade is finished 15:06:42 <spatel> https://platform9.com/kb/openstack/deleting-a-cinder-service-from-host 15:07:34 <noonedeadpunk> spatel: https://docs.openstack.org/cinder/latest/cli/cinder-manage.html#cinder-service 15:07:50 <spatel> do we need cinder-manager? 15:08:14 <spatel> How do i install cinder-manager? 15:09:31 <noonedeadpunk> I know that flags for rabbitmq must be enabled BEFORE the upgrade... Though, if we will backport and enable them after each one - we should be in a good shape... 15:09:50 <NeilHanlon> that seems at least logical to me 15:09:56 <noonedeadpunk> As it's kinda scary to enable flags before, since cluster might be in kinda unknown state consisting of multiple versions 15:10:09 <NeilHanlon> right... 15:10:10 <noonedeadpunk> or hell know what 15:10:53 <noonedeadpunk> looking at table of when flags introduced/become required - there's quite some margin there 15:11:21 <jrosser> andrewbonney: rabbitmq feature flags ^^ if you're around 15:12:03 <damiandabrowski> looks good, but it may still leave some users with a broken rabbitmq after upgrade, so maybe it's worth to mention in releasenotes what to do with this 15:12:12 <NeilHanlon> is it "safer" if it's done stepwise? i.e., backup, reset, upgrade, restore? 15:12:17 <damiandabrowski> in my case I just removed mnesia DB on second and third rabbitmq node 15:12:30 <NeilHanlon> or at least mention in release notes how to recover, and to make backups if needed 15:13:20 <noonedeadpunk> damiandabrowski: yes, totally worth having a release note with that 15:13:34 <noonedeadpunk> I'm not kinda afraid of Bobcat upgrades due to that 15:13:45 <noonedeadpunk> as quite some flags are required from 2.3.12 15:13:48 <noonedeadpunk> *3.12 15:15:46 <noonedeadpunk> and totally affecting 2023.1 with 3.11 requirements 15:16:21 <noonedeadpunk> other then that - I have proposed role branching already. so any potential fix will come as a backport to 2023.2 15:17:22 <noonedeadpunk> I hope roles will be branched really soonish and we can have tagged before deadline... 15:18:08 <noonedeadpunk> Despite we didn't have plenty of work - that made me feel relaxed and still we're on deadline :( So this time it's totally my fault and meantal gap kinda 15:21:56 <NeilHanlon> thanks for doing all that. Appreciate you! 15:23:01 <noonedeadpunk> In terms of outstanding patches that we need to land for 2023.2 15:24:05 <noonedeadpunk> I think we might have missed some important bits actually 15:24:23 <noonedeadpunk> Like Ironic might be failing when deployed in LXC without this: https://review.opendev.org/c/openstack/openstack-ansible-os_ironic/+/898253 15:24:35 <opendevreview> Dmitriy Rabotyagov proposed openstack/openstack-ansible-haproxy_server master: Convert haproxy_service_config_external.yml to a symlink https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/897841 15:25:28 <noonedeadpunk> then this would also made sense to appear for 2023.2 in octavia role: https://review.opendev.org/c/openstack/openstack-ansible-os_octavia/+/885519 15:25:51 <noonedeadpunk> compatability matrix: https://review.opendev.org/c/openstack/openstack-ansible/+/901191 15:27:21 <noonedeadpunk> And this thing: https://review.opendev.org/c/openstack/openstack-ansible/+/901534 15:27:43 <noonedeadpunk> I'm not 100% sure about it frankly speaking. It sounds reasonable and help handle CMQv2 logic 15:28:10 <noonedeadpunk> But resulting readability is not perfect 15:28:29 <noonedeadpunk> And I guess it should be somehow documented separately along with quorum queues 15:35:02 <noonedeadpunk> I think that this is pretty much everything I had on the table for today 15:35:03 <NeilHanlon> may not be a lot of _stuff_ this round, but it's complicated... that's for sure 16:03:24 <NeilHanlon> #endmeeting