15:01:04 <noonedeadpunk> #startmeeting openstack_ansible_meeting
15:01:04 <opendevmeet> Meeting started Tue Mar 22 15:01:04 2022 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:04 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:04 <opendevmeet> The meeting name has been set to 'openstack_ansible_meeting'
15:01:14 <noonedeadpunk> #topic rollcall
15:01:19 <noonedeadpunk> hey everyone
15:01:27 <noonedeadpunk> I'm half-there as have a meeting
15:04:55 <damiandabrowski[m]> hi!
15:08:10 <noonedeadpunk> #topic office hours
15:08:42 <noonedeadpunk> well, don't have much topics to have that said
15:08:53 <noonedeadpunk> we're super close to PTL and openstack release
15:09:11 <noonedeadpunk> * s/PTL/PTG/
15:10:05 <noonedeadpunk> So please register to PTG and let's fill in topics for discussion in etherpad
15:10:09 <noonedeadpunk> #link https://etherpad.opendev.org/p/osa-Z-ptg
15:10:44 <NeilHanlon> heya
15:12:45 <NeilHanlon> TY for the note about PTG!
15:14:41 <Brace> jamesdenton: nope, it doesn't get rebuilt on C2 and takes a disable/enable before it comes up on the other two, so I guess that leans towards rabbitmq being the issue?
15:17:31 <jamesdenton> well, or somehow the router is no longer scheduled against C2. can you try openstack network agent list --router <id>
15:18:24 <noonedeadpunk> other then that I didn't have time for anything else since week was quite tough with internal things going on
15:19:29 <Brace> jamesdenton: it's alive and up on all controllers according to that command
15:21:33 <jamesdenton> ok. it may be that the other routers are experiencing a similar condition
15:21:45 <jamesdenton> not sure if only C2 is to blame, but seems problematic anyway.
15:25:34 <Brace> yup
15:25:57 <jrosser> o/ hello
15:27:21 <opendevreview> Jonathan Rosser proposed openstack/ansible-role-pki master: Refactor conditional generation of CA and certificates  https://review.opendev.org/c/openstack/ansible-role-pki/+/830794
15:50:23 <Brace> jamesdenton: I'm going to try restarting l3-agent on C2 and see what that does, can't make things worse can it!
15:50:35 <jamesdenton> i guess not :D
15:50:54 <jamesdenton> tail the log after you restart it and see if there's anything unusual reported
15:51:16 <jamesdenton> main loop exceeding timeout or anything along those lines
15:57:14 <Brace> jamesdenton: I wouldn't know what's unusual tbh, but there's an note about finding left over processes which indicates an unclean termination of a previous run
15:57:53 <jrosser> oh well now that is a thing with systemd isnt it?
15:58:17 <Brace> not sure tbh, but it otherwise seems ok
15:59:33 <jrosser> this https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/772538
15:59:36 <Brace> but the router still doesn't come back on c2
15:59:50 <jrosser> and https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/781109
16:00:36 <jrosser> so restarting the netutron agent does not necessarily remove all the things that it created
16:00:47 <jamesdenton> Brace you might try unscheduling the router from the agent, and rescheduling to see if it will clean up and recreate
16:01:01 <Brace> ah, I just tried disabling and enabling the port
16:01:10 <Brace> router even
16:01:15 <jamesdenton> right, ok.
16:01:30 <jamesdenton> try to unschedule and reschedule. i cannot remember offhand the command
16:01:42 <jamesdenton> i'm headed OOO for the day
16:02:27 <Brace> jamesdenton: thank you for all your help, much appreciated
16:02:39 <Brace> I'll try the unschedule and reschedule
16:04:40 <noonedeadpunk> #endmeeting