18:00:11 #startmeeting tc 18:00:11 Meeting started Tue Sep 19 18:00:11 2023 UTC and is due to finish in 60 minutes. The chair is JayF. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:11 The meeting name has been set to 'tc' 18:00:21 o/ 18:00:31 Hello TC members and friends, welcome to today's TC meeting 18:00:33 o/ 18:00:41 o/ 18:00:57 A reminder that this meeting is held under the OpenInfra Code of Conduct available at https://openinfra.dev/legal/code-of-conduct 18:01:05 Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee 18:01:08 #topic Roll Call 18:01:10 o/ 18:01:14 o/ 18:01:16 o/ 18:01:17 looks like most of you beat me to the punch :D 18:01:20 o/ 18:01:46 going to give a minute or two for more to join 18:02:38 I'll note knikolla is an expected absense; I hope he gets well soon 18:02:58 o/ for the record 18:03:21 #note No action items from previous meeting. 18:03:26 #topic Gate health check 18:03:30 How is the gate doing? 18:04:03 it is good this week, have not seen much failure 18:04:28 Thank you to those keeping things running smoothly for release. Going to allow a minute or so for anyone to surface any issues before I move to the next topic. 18:04:33 "much" is subjective, 18:04:36 but yeah not too bad 18:04:45 I think the neutron thing is fixed now right? 18:04:51 there was some stestr issue, but it only affected jobs not using u-c 18:05:27 and also was fixed within hours by a new stestr release 18:05:30 dansmith what neutron thing exactly? 18:05:50 yeah, doc jobs somwhere was having same issue of not using u-c 18:06:00 there was a test that was failing a lot and there was a fix, revert, etc going on 18:06:13 this: https://bugs.launchpad.net/neutron/+bug/1940425 18:06:17 yeah trunk test, it is skipped now 18:06:30 yeah, so that was a big problem, but cool 18:06:37 i mean marked as unstable so test result is non voting 18:07:00 python 3.11 testing is failing for many projects, https://zuul.openstack.org/builds?job_name=openstack-tox-py311&result=POST_FAILURE&result=FAILURE&result=RETRY_LIMIT&result=ERROR&skip=0 18:07:19 it is going to be voting for next cycle in couple of weeks, I will send another reminder on ML 18:07:24 or try to fix a few if i get time 18:07:41 gmann: many of those are likely to be bindep fixes needed; I'll bookmark that too and try to fix a few. 18:07:48 dansmith ahh, k 18:08:01 JayF: perfect, thanks 18:08:05 Anything further about gate status? 18:08:11 yeah, there are very less code error and only in few projects 18:08:47 we did end up dropping a stable/stein job for the requirements repo because it was preventing rocky branch cleanup 18:09:14 thanks for cleaning up rocky and reporting about that changed job 18:09:21 requirements was running a sdk source integration job in stein which was parented to a job definition that only lived on stable/rocky 18:09:45 and the other jobs for stein were so busted we ended up just bypassing gating to merge that 18:09:53 yeah, there might be some other project failing for same and solution is simple to swicth to new job 18:11:12 This is the only item on the agenda before open discussion so I'm happy to allow as much time as it needs but I think we've wound down? 18:11:55 #topic Open Discussion and Reviews 18:11:58 yup 18:12:17 #link https://openinfra.dev/ptg/ Please ensure you have registered for the PTG 18:12:42 and a reminder to have a look at open governance changes #link https://review.opendev.org/q/projects:openstack/governance+is:open 18:12:45 #link https://review.opendev.org/q/projects:openstack/governance+is:open 18:12:48 also elections close in a little over a day 18:12:49 #link https://review.opendev.org/q/projects:openstack/governance+is:open 18:12:53 there we go, sorry for the spam 18:13:42 i think the election officials were planning to send a mid-poll reminder to openstack-discuss and then got busy with other things, so another nudge might help 18:13:45 looks like there are some meaningful items in governance repo; I will do a review pass after the meeting and suggest others do the same 18:13:56 fungi: it closes in about 27 hours, is it too late already? 18:14:16 I would be +1 to someone from TC or election official sending such a reminder; I'd rather it be someone not running in this election though (e.g. not me) 18:14:23 a one-day-remaining reminder could still do some good to get a few last-minute votes, maybe 18:14:38 election officical send the reminder like 1-2 days before 18:14:40 fungi's reminder in a meeting I was in this morning prompted me to finally get it done 18:14:44 so ya I would say remind people now 18:15:33 Given I don't know if there's anyone even active in this meeting on the TC who is not running this cycle; I'll send that email since nobody else has volunteered. 18:15:56 I don't see any problem iwth candidates reminding people to vote 18:16:00 JayF: or we can remind election official to send 18:16:26 I think ianychoi[m] is pretty much on top of those reminder and notificaiton 18:16:31 gmann: given time constraints I think it's best that it gets done closer to now; and I assume if they missed it like usually is done they are likely busy 18:17:00 ah, yeah. 18:17:11 both officials are in apac usually, so may not be awake yet 18:17:32 ianychoi[m]: is usually online this time let's see if he reply/send in an hr or so other JayF can send 18:17:44 I'm happy to wait until the top of the hour 18:18:46 I'm going to generally note; I don't show an election reminder email in my openstack-discuss (local) archives for previous elections 18:19:03 Last call for new items for Open Discussion? 18:19:03 seems like there were reminder in election IRC channel on 18and today 18:20:12 Last chance before I close the meeting? 18:20:23 release is looking happy other than the gate? 18:20:27 did anyone have any comments about the openinfra foundation bylaws changes that we talked about last week? 18:20:59 ah yeah, thanks rosmaita for reminder 18:21:13 we will be meeting today, please respond to email if there is more feedback 18:21:14 also, i see "voting 24 hours remain" from fungi on 2020-10-12, so there is a precedent 18:22:07 gmann can I get the info for that? I’ll try to attend 18:22:20 Yeah, lets get that foundation meeting in the meeting notes, that's useful 18:22:40 spotz[m]: yeah, i just remineded myself for that, forwarding you 18:22:54 gmann: is there a public link to info about that which I can #link for the minutes? 18:23:07 its zoom call, anyone can join. let me know if you would like to join and I will forward the invite 18:23:11 sure 18:23:46 this is etherpad of discussion #link https://etherpad.opendev.org/p/openstack-tc-charter%2Bbylaws-scratchpad 18:23:52 #note OpenDev Foundation meeting today; TC feedback on bylaws changes due to be consumed. Interested parties can contact gmann for information about how to attend if they wish. 18:24:06 s/opendev/openinfra/ 18:24:12 #undo 18:24:12 Removing item from minutes: #link https://review.opendev.org/q/projects:openstack/governance+is:open 18:24:20 The note didn't take? 18:24:25 #link https://review.opendev.org/q/projects:openstack/governance+is:open 18:24:30 i think you wanted info not note 18:24:33 ty 18:24:40 #info OpenInfra Foundation meeting today; TC feedback on bylaws changes due to be consumed. Interested parties can contact gmann for information about how to attend if they wish. 18:24:52 Anything further? 18:25:01 clarkb: regarding the release, the oslo.db situation seems to be well under control, a new release has been proposed that will work with (hopefully) all projects in bobcat 18:25:21 frickler: excellent 18:25:36 sweet 18:25:38 thx to stephenfin for doing some reduced semi-reverts there 18:25:47 I was expecting that to come up here if it wasn't resolved 18:26:02 for castellan I proposed a stack of reverts that still need more reviews 18:26:06 * bauzas waves and sits in the back 18:26:08 I saw those changes, they were great. Thank you all for managing them. 18:26:18 (the oslo.db semi-reverts) 18:26:22 yeah, thanks 18:26:30 Thanks folks for fixing it 18:27:37 some projects still need their rc1 and branch, but I'm not sure how close we are to the deadline for that 18:28:01 well past 18:28:07 frickler: it's my understanding the final deadline is a week from Friday; Ironic has many of the cycle-with-intermediary projects and we have intentions on cutting releases Thursday. 18:28:28 seems so, I need to do same for tempest 18:28:46 rc1 target week for services was last week 18:28:57 which is when branches are supposed to be created 18:28:58 yeah we had issues in Nova due to the CI failures 18:29:11 Final RC deadline: September 28th, 2023 (R-1 week) 18:29:33 final rcs are typically >1 and tagged on the stable branch 18:29:34 That's why we only had the RC1 today 18:29:39 Which is also (in my understanding) the deadline for when cycle-with-intermediary projects need to be branched and released 18:30:05 (28/Sept/2023) 18:30:44 I don't think there's anything actionable in this discussion; things are progressing. 18:30:48 yeah, when i said "for services" i meant cycle-with-milestone or whatever the current name is 18:31:19 fungi: ack; I'm being defensive here because I can't find explicit documentation on when my release is due so I want to know if we are "late" 18:31:31 (I don't think we are, to be claer) 18:31:32 libs and clients were supposed to be branched far earlier 18:31:53 so as of last week almost everything (except with intermediary and trailing) should have been branched 18:32:06 That matches my understanding :D 18:32:39 Is there anything new for open discussion before I close the meeting? 18:34:23 #endmeeting