15:00:15 <yoctozepto> #startmeeting tc
15:00:15 <opendevmeet> Meeting started Thu Feb  3 15:00:15 2022 UTC and is due to finish in 60 minutes.  The chair is yoctozepto. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:16 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:16 <opendevmeet> The meeting name has been set to 'tc'
15:00:22 <yoctozepto> #topic Roll call
15:00:23 <yoctozepto> \o/
15:00:24 <dansmith> o/
15:00:37 <spotz> o/ sorta
15:00:59 <jungleboyj> o/
15:01:05 <yoctozepto> there is an apologies entry for spotz and ricolin but spotz is here nonetheless, welcome!
15:01:42 <yoctozepto> counting 4 members
15:01:48 <yoctozepto> will there be quorum today
15:02:07 <yoctozepto> belmoreira seemingly not around
15:02:19 <jungleboyj> Thought we were supposed to do a video meeting today.
15:02:35 <yoctozepto> mnaser is on the openinfra live
15:02:42 * jungleboyj not that I am complaining
15:02:43 <yoctozepto> seemingly along with belmoreira
15:02:49 <mnaser> yoctozepto: belmoreiro is hosting with me yes :p
15:02:52 <mnaser> (sorry)
15:03:09 <yoctozepto> jungleboyj: yeah, we (with gmann) changed to make it more accessible
15:03:17 <jungleboyj> Awesome.
15:03:33 <yoctozepto> mnaser: yeah, no problem, that time conflict is something to resolve in the future
15:04:40 <dansmith> so, quorum or no?
15:04:58 <yoctozepto> seems no quorum
15:05:09 <spotz> It's handy when we're on the show as a group but sucks when it's 1 here and 1 there
15:05:20 <yoctozepto> spotz: indeed
15:05:31 <jungleboyj> We can quarrel.
15:05:32 <yoctozepto> we can continue with no decision powers I guess
15:05:37 <yoctozepto> lol
15:06:10 <yoctozepto> diablo_rojo_phone: around?
15:06:27 <yoctozepto> _phone suggests not
15:06:47 <yoctozepto> ok, let's continue for the sake of having discussions today
15:07:35 <yoctozepto> #topic Follow up on past action items
15:07:40 <yoctozepto> but there were none
15:07:50 <yoctozepto> #topic Gate health check
15:07:59 <yoctozepto> ** Fixing Zuul config error in OpenStack
15:07:59 <yoctozepto> *** https://etherpad.opendev.org/p/zuul-config-error-openstack
15:08:00 <dansmith> the qos thing si resolved?
15:08:14 <dansmith> that was biting several of us for a few days
15:08:27 <yoctozepto> dansmith: no idea, I know nova-next is practically broken
15:08:34 <yoctozepto> (read about that on the ml)
15:08:40 <dansmith> yeah but being worked on, that only affects nova though IIRC
15:08:46 <yoctozepto> and devstack gate
15:08:47 <diablo_rojo_phone> Hosting open infra live so I'm a bit spotty
15:08:48 <dansmith> the qos one was breaking lots of people
15:08:51 <diablo_rojo_phone> Sorry!
15:09:03 <yoctozepto> diablo_rojo_phone: ack, enjoy it
15:09:12 <dansmith> throughput has been good, except monday (or tuesday?) it was somewhat backed up,
15:09:21 <dansmith> but no complaints from me.. seems pretty decent lately
15:09:33 <yoctozepto> (seems 3 members captured by openinfra live, one holidays, one sick)
15:09:54 <yoctozepto> dansmith: ack, thanks
15:10:11 <jungleboyj> We had some issues with the Stable gates this week but I think those have been worked out as well.
15:10:45 <yoctozepto> great, thanks for reporting
15:11:14 <yoctozepto> so
15:11:18 <yoctozepto> on the zuul config errors
15:11:35 <yoctozepto> seems some projects working diligently on fixing them
15:11:43 <yoctozepto> others not so much
15:11:53 <dansmith> I don't even know what the issue is?
15:12:07 <yoctozepto> dansmith: infra asked us to clear up https://zuul.opendev.org/t/openstack/config-errors
15:12:19 <yoctozepto> it's ridiculously long
15:12:33 <yoctozepto> the progress (along with details) is tracked here: https://etherpad.opendev.org/p/zuul-config-error-openstack
15:12:49 <dansmith> man that's a list
15:12:55 <yoctozepto> yup
15:13:19 <jungleboyj> Yikes.
15:13:32 <dansmith> seems mostly networking?
15:13:35 <yoctozepto> I think we really need a person from TC to watch over this progress
15:13:54 <yoctozepto> dansmith: hard to tell for sure
15:13:56 <yoctozepto> but looks like it
15:14:15 <dansmith> can we make a list of all the repos those jobs are in?
15:14:16 <yoctozepto> https://review.opendev.org/c/openstack/releases/+/818207
15:14:22 <yoctozepto> they seemed to have eoled these branches
15:14:30 <yoctozepto> so no idea why this bugs the zuul still
15:14:30 <dansmith> because it's hard to tell, and that would surely be a smaller list
15:14:51 <dansmith> ah, I see the etherpad has a smaller list of projects
15:14:59 <yoctozepto> yeah, it's been parsed
15:15:47 <yoctozepto> fungi, clarkb: you around? :-) it seems eoling old neutron/networking branches did not help with zuul errors
15:16:27 <yoctozepto> I mean, it is hard to tell which are still affected
15:16:33 <yoctozepto> guessing eoled ones are not
15:16:42 <fungi> eol'ing branches without eol'ing the branches of other projects using things from them is what creates a lot of those errors
15:17:12 <yoctozepto> ah, that makes sense
15:17:27 <fungi> we used to eol across the board in every repo
15:17:57 <fungi> these days it's on-demand and some projects are asking to have branches eol'd which contain things used by other projects who aren't asking to have the same branches eol'd
15:18:23 <yoctozepto> messy
15:18:35 <fungi> so those branches are effectively broken and untestable, but nobody's paying attention to them anyway
15:18:55 <fungi> in short, better cleanup would help
15:19:13 <dansmith> does this actually hurt anything? other than maybe making that config errors page less useful for actual errors?
15:20:41 <fungi> pretty much that
15:20:46 <dansmith> ack
15:20:56 <fungi> and it's an indication of essentially abandoned projects/branches in openstack
15:21:55 <dansmith> well, looks like neutron and ironic are probably the biggest of the ones I know how to contact
15:22:09 <yoctozepto> well, I guess the TC does not have the bandwidth to go and fix it for the projects; the projects are aware and... that's it I guess?
15:22:34 <dansmith> well, I was just thinking about a little tree-shaking,
15:22:44 <dansmith> and that would be the most helpful for the biggest offenders
15:24:26 <dansmith> oh I guess only two from ironic
15:24:29 <yoctozepto> neutron/networking has 33 entries
15:24:38 <dansmith> yeah, neutron is the big one
15:24:44 <yoctozepto> ironic 4 entries
15:25:18 <yoctozepto> manila 1
15:25:35 <dansmith> I only see two from ironic, what are the others?
15:26:11 <dansmith> nm I see
15:26:20 * gouthamr takes note on the manila job
15:26:30 <gouthamr> #link https://review.opendev.org/c/openstack/python-manilaclient/+/825068
15:26:33 <gouthamr> will be merged soon
15:26:54 <fungi> i think one of the big cases for netron was that a project (driver?) was retired but not removed from job configs
15:27:13 <fungi> er, neutron. though netron is a humorously appropriate typo
15:27:39 <dansmith> yoctozepto: we should probably do this async to the meeting
15:28:01 <dansmith> yoctozepto: I rang the ironic bell, so hopefully we'll get some action there.. four entries should be not too bad
15:28:05 <yoctozepto> ok, I finished with the current list
15:28:15 <yoctozepto> but there seems to be more projects affected
15:28:21 <dansmith> they were was blissfully ignorant as I was until the top of this hour :)
15:28:23 <yoctozepto> as there are 79 entires in total
15:28:31 <yoctozepto> dansmith: haha
15:28:43 <yoctozepto> thanks for letting them know
15:29:17 <yoctozepto> thanks gouthamr
15:29:37 <yoctozepto> ok, we made some progress
15:29:43 <yoctozepto> even without the quorum
15:29:45 <yoctozepto> :-)
15:29:54 <yoctozepto> let's switch to the next topic
15:30:17 <yoctozepto> #topic Progress check on Yoga tracker
15:30:23 <yoctozepto> ** https://etherpad.opendev.org/p/tc-yoga-tracker
15:31:07 <yoctozepto> technical guidelines seem to have stalled
15:31:13 <yoctozepto> is that right, spotz?
15:31:26 <dansmith> that was my deal actually
15:31:32 <dansmith> and yeah, I suck
15:31:43 <spotz> yoctozepto: Yeah I did the original ask but then we semmed to change what we wanted and it made sense to just put it on hold
15:31:47 <jungleboyj> Wow, that took a turn.
15:32:22 <yoctozepto> yeah
15:32:58 <yoctozepto> point 2 is gate health check that we hvae done
15:33:14 <yoctozepto> point 3 is what I'm working atm
15:33:35 <yoctozepto> there is one issue to be aware of - the releases team is relying on one of the tags (stable policy)
15:33:58 <yoctozepto> it's well documented so I need to restore that tag for the time being
15:34:45 <yoctozepto> I have nothing else to report, there should be a new rev of the change proposed today
15:34:49 <yoctozepto> mergable this time
15:35:30 <yoctozepto> folks for 4,5,6 not present
15:35:49 <yoctozepto> point 7 is at jungleboyj
15:35:59 <jungleboyj> I should be able to get to the Survey feedback next week hopefully.
15:36:00 <yoctozepto> please speak up, Tarzan
15:36:06 <yoctozepto> thanks jungleboyj
15:36:11 <jungleboyj> yoctozepto: ha ha.
15:37:01 <yoctozepto> ok, we have reviewed the progress on the yoga tracker
15:37:17 <yoctozepto> #topic Z Release Cycle Name
15:37:24 <yoctozepto> ** Election results:
15:37:24 <yoctozepto> https://civs1.civs.us/cgi-bin/results.pl?id=E_693bd8bbe63ca52f
15:37:24 <yoctozepto> ** Next step, the foundation has started the trademark checks.
15:37:35 <jungleboyj> Yay!
15:37:50 <yoctozepto> I *really* hope Zen will pass
15:38:04 <yoctozepto> as I will deny to work on a Zombie project
15:39:28 <yoctozepto> I guess nothing more to say on that!
15:39:39 <yoctozepto> #topic Z cycle Technical Elections
15:39:50 <yoctozepto> ** Proposed Election schedule, need to merge it if no objection.
15:39:50 <yoctozepto> *** https://review.opendev.org/c/openstack/election/+/825017
15:40:08 <yoctozepto> I'm not an election official
15:40:13 <yoctozepto> so can't +2
15:40:19 <yoctozepto> but I guess there are no objections
15:40:35 <yoctozepto> jungleboyj, spotz: can you comment on that?
15:40:59 <yoctozepto> this is prime time it gets merged
15:41:48 <spotz> yoctozepto: I can +w if diablo_rojo_phone doesn't have anything on it
15:42:12 <jungleboyj> Do we need to wait for the release name?  That was the thing I thought was holding it up.
15:42:24 <jungleboyj> Otherwise, I am fine with it.
15:42:32 <spotz> Oh good question not sure
15:42:43 <yoctozepto> I did not understand it like this
15:42:58 <yoctozepto> fungi: may you help? you know pretty much everything related to these processes
15:43:05 <jungleboyj> He he.
15:44:55 <fungi> the q is whether we need a release name before we approve an election schedule?
15:45:07 <yoctozepto> fungi: yeah
15:45:25 <yoctozepto> I think we can fix it later
15:45:28 <fungi> it's all a matter of communications, yes
15:45:29 <yoctozepto> both there and in comms
15:45:35 <yoctozepto> ++
15:45:37 <fungi> we can say "z cycle" and use a placeholder
15:45:38 <yoctozepto> thanks fungi
15:45:48 <jungleboyj> Ok.  Then we should probably merge that.
15:45:52 <fungi> it gets harder if we need to fix it after we start accepting nominations
15:45:55 <yoctozepto> my thoughts exactly
15:46:12 <fungi> but this early it's not critical yet
15:46:22 <yoctozepto> diablo_rojo_phone: no objections against the schedule?
15:48:33 <yoctozepto> guess she's too busy being the live hostess
15:48:42 <yoctozepto> no problem, we can do it after the meeting
15:48:52 <yoctozepto> #topic Open Reviews
15:49:15 <yoctozepto> https://review.opendev.org/q/projects:openstack/governance+is:open
15:49:33 <yoctozepto> my WIP will change later today, please feel very welcome to review then
15:49:48 <yoctozepto> other than that
15:49:55 <yoctozepto> we have two from ricolin that have stalled
15:50:00 <yoctozepto> and ricolin not around today
15:50:08 <yoctozepto> and one test change
15:50:21 <yoctozepto> from lourot
15:50:54 <yoctozepto> so nothing to review atm
15:50:55 <yoctozepto> good job
15:51:09 <yoctozepto> #topic Open discussion
15:51:20 <yoctozepto> we have ~9 minutes if you want to discuss something in general
15:51:29 <yoctozepto> otherwise I will close the meeting
15:52:52 <dansmith> doeeet!
15:53:08 <yoctozepto> #endmeeting