17:00:05 #startmeeting F36 Final Go/No-Go meeting 17:00:05 #meetingname F36-Final-Go_No_Go-meeting 17:00:05 Meeting started Thu May 5 17:00:05 2022 UTC. 17:00:05 This meeting is logged and archived in a public location. 17:00:05 The chair is bcotton. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 17:00:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:05 The meeting name has been set to 'f36_final_go/no-go_meeting' 17:00:05 The meeting name has been set to 'f36-final-go_no_go-meeting' 17:00:19 #topic Roll Call 17:00:27 morning everyone 17:00:27 .hi 17:00:28 salimma: salimma 'Michel Alexandre Salim' 17:00:36 .hello humaton 17:00:37 jednorozec: humaton 'Tomáš Hrčka' 17:00:47 .hello copperi 17:00:48 copperi[m]: copperi 'Jan Kuparinen' 17:00:55 .hello churchyard 17:00:56 mhroncok: churchyard 'Miro Hrončok' 17:01:00 .hello CRCinAU 17:01:01 CRCinAU: crcinau 'Steven Haigh' 17:01:11 * mhroncok is here, but will likely go away really soon 17:01:26 .hello geraldosimiao 17:01:27 geraldosimiao: geraldosimiao 'Geraldo S. Simião Kutz' 17:01:34 .hello 17:01:34 coremodule: (hello ) -- Alias for "hellomynameis $1". 17:01:41 .hello2 17:01:42 coremodule: coremodule 'Geoffrey Marr' 17:02:13 .hello mohanboddu 17:02:14 mboddu: mohanboddu 'Mohan Boddu' 17:02:43 big attendance today. i should have put on a tie 17:03:05 * salimma is wearing a three-piece suit 17:03:08 * mattdm is here with my Go-Stick 17:03:11 I challenge anyone to prove me wrong 17:03:13 .hello adamwill 17:03:14 adamw: adamwill 'Adam Williamson' 17:03:16 we'll wait another moment to see who else rolls in and then we'll start 17:04:00 #topic Purpose of this meeting 17:04:00 #info Purpose of this meeting is to check whether or not F36 Final is ready for shipment, according to the release criteria. 17:04:07 #info This is determined in a few ways: 17:04:07 #info 1. No remaining blocker bugs 17:04:07 #info 2. Release candidate compose is available 17:04:07 #info 3. Test matrices for Beta are fully completed 17:04:24 #topic Current status - blockers 17:04:40 #info 1 Proposed Blockers 17:04:40 #info 4 Accepted Blockers 17:04:40 #info 0 Accepted 0-day Blockers 17:04:40 .hello t0xix0der 17:04:41 t0xic0der[m]: Sorry, but user 't0xix0der' does not exist 17:04:48 .hello t0xic0der 17:04:48 #topic (2081326) The terminal does not show username and hostname on the terminal prompt 17:04:48 #link https://bugzilla.redhat.com/show_bug.cgi?id=2081326 17:04:48 #link https://pagure.io/fedora-qa/blocker-review/issue/806 17:04:48 t0xic0der[m]: t0xic0der 'Akashdeep Dhar' 17:04:48 .hello2 17:04:51 Alessio[m]: Sorry, but user 'Alessio [m]' does not exist 17:04:58 #info Proposed Blocker, gnome-terminal, NEW 17:04:59 #info Ticket vote: FinalBlocker (+2,0,-11) (+asciiwolf, +jpbn, -catanzaro, -bcotton, -geraldosimiao, -mattdm, -humaton, -somethingsomethingfedora, -nb, -coremodule, -kparal, -augenauf, -sgallagh) 17:04:59 #info Ticket vote: FinalFreezeException (+3,0,-0) (+bcotton, +somethingsomethingfedora, +nb) 17:05:11 .hi 17:05:12 nb: nb 'Nick Bebout' 17:05:32 all indications are that this was some kinda crazy bitflip event 17:05:32 this may be a record for number of ticket votes. the -1s have a clear majority, but since it's still on the list, i figured we should see if anyone can make a case for accepting it 17:05:50 Ben Cotton (he/him): i figured at this point we should just save it for this meeting to be sure 17:06:06 agreed on both counts 17:06:22 but i'm -1 just on the basis that we've been installing f36 a lot for months and hit this once. or twice. depends if this and the person in irc were the same thing. 17:06:25 yeah, -1 FinalBlocker... seems to have gone away/not be reproducable 17:07:03 if someone else does run into it we'll just have to tell 'em to reinstall. 17:07:22 no easy way to fix manually? 17:07:49 robatino: well, you could copy the stuff from /etc/skel in manually i guess, but if that wasn't done, who knows what else might be funky...personally i'd just reinstall, at least if i caught it right away. 17:07:50 adamw: Creating a new user is enough, no? 17:07:54 I'll keep my vote the same as already in the ticket 17:07:57 kparal: oh, yeah, or that. 17:08:08 proposed #agreed 2081326 - RejectedBlocker (Final) - This bug has no clear reproducer and seems to be extraordinarily rare. 17:08:18 Ack 17:08:21 ack 17:08:24 I'll mark that with CommonBugs and add some advice how to fix it 17:08:24 Ack 17:08:29 ack 17:08:30 ack 17:08:40 kparal: I'm not even sure we should commonbugs it 17:08:44 kparal: I'm not sure it's even commonbugs worthy 17:08:48 jinx 17:08:52 any documentation is good documentation. 17:08:55 meaning it's that rare, or why? 17:09:01 It's anything but common 17:09:11 mattdm: that's not going to help the rumor that you're just a puppet i control :p 17:09:14 I'm not sure it's even _rare_ — rather maybe "a fluke" 17:09:15 Rarebugs 17:09:20 it should go on the rarebugs page 17:09:29 even if its phrased as "We've seen X, but only occasionally, and we can't reproduce it. If you see it, do Y to fix" 17:09:32 Flukebugs 17:09:42 ack 17:09:42 ok, adamw to create a rarebugs page and document it 17:09:46 #agreed 2081326 - RejectedBlocker (Final) - This bug has no clear reproducer and seems to be extraordinarily rare. 17:09:50 ack 17:09:51 ack 17:09:54 ack 17:09:56 ack 17:10:00 #topic (2079344) A new album looks empty until app restart 17:10:00 #link https://bugzilla.redhat.com/show_bug.cgi?id=2079344 17:10:00 #link https://pagure.io/fedora-qa/blocker-review/issue/787 17:10:00 #info Accepted Blocker, gnome-photos, VERIFIED 17:10:01 ack 17:10:02 i seem to have remembered an extremely important appointment i had 17:10:11 this is fixed. 17:10:15 anyone care to say this isn't fixed? 17:10:41 I'm guessing the Online Accounts part of photos being b0rked is well out of scope for consideration? 17:10:54 It's fixed 17:10:54 * kparal has some stuff to attend to, very urgently 17:10:54 #topic (2081291) album picker duplicates fields, preventing photo organization 17:10:54 #link https://bugzilla.redhat.com/show_bug.cgi?id=2081291 17:10:54 #link https://pagure.io/fedora-qa/blocker-review/issue/802 17:10:54 #info Accepted Blocker, gnome-photos, VERIFIED 17:10:55 ditto this one 17:11:05 yay! 17:11:12 CRCinAU: it's too late for consideration! 17:11:14 this train is leaving 17:11:22 yup, this is fixed too 17:11:25 thought as much. 17:11:27 #topic (2056303) After upgrade to F36 several packages fail to update due to selinux-related errors 17:11:27 #link https://bugzilla.redhat.com/show_bug.cgi?id=2056303 17:11:27 #link https://pagure.io/fedora-qa/blocker-review/issue/756 17:11:27 #info Accepted Blocker, selinux-policy, ON_QA, depends on other bugs 17:12:17 this was fixed in -7 I think? 17:12:42 we were keeping an eye on it to make sure updates went to f34 and f35 and nobody claimed any more problems 17:13:00 we really need -7 to be good enough for this, because -8 didn't make the compose :| but i think it is. 17:13:12 yeah, thats one of the two things I was going to note. ;( 17:13:43 #info -7 should have a good enough fix for this 17:13:53 I just wonder how many verification test I performed were with -7 and how many with -8 17:14:11 kparal: from the bug you mention -7 several times, never -8 17:14:21 selinux-policy-36.7-1.fc36 is in the compose, selinux-policy-36.8-1.fc36 is supposed to be in stable... but it only fixes FE's 17:14:26 and i don't think any change in -8 is listed as relevant to this 17:14:30 but it shouldn't matter for upgrades, I realize. Upgrades will always get -8 17:15:07 oh yes that's a good point 17:15:08 whew 17:15:19 this bug was about upgrades, so it doesn't matter what was on the media 17:15:20 should be good (tm) 17:15:20 proposed #agreed 2056303 is fixed for the purposes of the release criteria 17:15:23 anyone disagree with that? 17:15:25 akc 17:15:27 ack 17:15:27 ack 17:15:30 ack 17:15:31 ack 17:15:32 we can probably close it 17:15:35 ack 17:15:35 ack 17:15:36 ack 17:15:55 #agreed 2056303 is fixed for the purposes of the release criteria 17:15:56 Ack 17:16:00 #topic (2072070) Connection to wireless network fails without explanation when other end does not support secure renegotiation 17:16:00 #link https://bugzilla.redhat.com/show_bug.cgi?id=2072070 17:16:00 #link https://pagure.io/fedora-qa/blocker-review/issue/729 17:16:00 #info Accepted Blocker, wpa_supplicant, ON_QA 17:16:09 this is also confirmed fixed. 17:16:15 hurray 17:16:23 Yay 17:16:25 from the comments i've seen, people who could reproduce this report fixes 17:16:27 As described on bug ticket, it's fixed 17:16:48 in #c44 17:17:04 oh 17:17:08 so, i do have a point to bring up here 17:17:15 point away 17:17:20 it's generally agreed that we didn't fix this, we worked around it 17:17:52 i wanted a subject matter expert to review the workaround, but none of the rh ones have really stepped in. so I mailed Jouni, the upstream author 17:18:22 I did notice something weird on wifi..... 17:18:34 his take on this is nuanced, but the big picture points are: 1) he would not want to assert that the workaround definitely does not reduce security. he thinks it's at least theoretically possible that in some cases, the workaround does potentially do that 17:18:56 So my network supports WPA2 + WPA3. If I set Gnome to use WPA3 Personal, it won't connect - but WPA2 Personal connects ok but the status shows WPA3.... 17:18:57 2) it's at least definitely no less secure than f35 was. the workaround effectively does what was already done on f35 (and earlier) 17:19:07 so I really dunno wtf its actually supposed to mean these days 17:19:20 i think point 2 makes me ok with shipping this, but did want to note that. 17:19:26 and see if anyone is concerned about point 1. 17:19:52 the "real" fix here would be something more targeted that lets the user allow legacy renegotiation only for a specified network. but we definitely didn't have time to implement that. 17:19:58 * nirik is ok with that, hopefully subject matter experts will weigh in and adjust this before f37 if needed. 17:20:32 adamw: I remember raising an issue like this a good 5 or so years ago 17:20:34 I noticed the workaround too late, but if additional testing is needed, happy to test and report back (our corporate fleet is affected) 17:20:51 yeah, i'm comfortable with that. a real fix is more of an RFE than a bugfix, imo 17:20:53 Michel Alexandre Salim 🎩: more testing can't hurt. 17:21:11 I'm with nirik @nirik:libera.chat: on that 17:21:16 where there should be a different set of toggles for wifi infrastructure..... as this kinda thing gets difficult and doesn't get replaced as quick as Fedora disables protocols / ciphers 17:21:19 oh yeah, another point jouni made is there may be further similar-but-not-the-same cases which this workaround won't address; i don't think we want to get into speculatively allowing more legacy stuff ahead of bug reports, though. we just need to be on the lookout for such cases. 17:22:00 * nirik nods 17:22:22 proposed #agreed 2072070 is sufficiently worked around for the purposes of the release criteria 17:22:23 So there needs to be a seperation between 'internet' security and 'let me connect to wifi' security. 17:22:31 ack 17:22:33 ack 17:22:36 but yes, that's a long term RFE / think about 17:22:39 Ack 17:22:40 ack 17:22:40 ack 17:22:43 ack 17:22:50 ack 17:22:50 ack 17:22:57 ack 17:23:27 #agreed 2072070 is sufficiently worked around for the purposes of the release criteria 17:23:27 ack 17:23:36 #topic Current status - blockers 17:23:38 #info All accepted blockers are sufficiently resolved 17:23:52 yaaay 17:23:58 #topic Current status - test matrices 17:23:58 #link https://fedoraproject.org/wiki/Category:Fedora_36_Test_Results 17:23:59 excellent 17:24:38 coverage looks really good. don't really have anything to note. 17:24:49 i just want to thank tflink and sgallagh for the fact that we have two consecutive weeks of not needing to pause the meeting to run AD tests 17:24:59 only a few spaces where we haven't run a test on one arch, but they're all ones where there's no reason to imagine it'd be broken on just one arch. 17:25:06 Excellent 17:25:12 oh, and we don't have any openstack cloud tests. buuuut it's probably fine... 17:25:12 Hooray for backhanded compliments! 17:25:26 Ship it! 17:25:35 Yes 17:25:39 Ship it! 17:25:49 I've got one thing to note about the compose... aside the selinux issue... 17:26:06 #info Test coverage is good. There are a few missing tests which are not concerning 17:26:07 #topic Current status - RC 17:26:11 fedora-cloud-base-gcp image failed due to a network issue. 17:26:19 * sgallagh quickly hits nirik with a sedative 17:26:21 all other artifacts are there. 17:26:26 nirik can we re-run just that artifact? 17:26:28 not quickly enough :-( 17:26:38 #info RC 5 is the current release candidate 17:26:38 sorry, I'll wait... 17:26:58 #info fedora-cloud-base-gcp is the only missing image (failed due to network issue) 17:27:07 no, nirik, your timing was perfect :-) 17:27:30 nb: no. we could use the nightly one tho if we desired. I am not sure how much that image is used or when/who uploads it. 17:28:09 It's a non-blocking deliverable, yes? 17:28:21 +1 for using the nightly one 17:28:30 yes, it's not blocking in any way. I just wanted to note it... 17:28:50 anything other questions or comments on RC 5? 17:28:55 perhaps use RC4 image instead of RC5? 17:29:18 there was no cloud-related change there 17:29:35 Good idea too 17:29:44 good idea 17:30:13 bcotton: I found the rc5 a good improvement over others 17:30:15 kparal: We will push all the updates stable and will run nightly compose for a day or two to have the last nightly content same as the GOLD RC, so better use nightly 17:30:49 #topic Go/No-Go decision 17:30:57 here comes the fun part! 17:30:59 FESCo? 17:31:01 go 17:31:03 kparal: But again, if no cloud-related changes, we can use either 17:31:05 Go 17:31:06 Go1 17:31:16 Releng? 17:31:19 Go 17:31:19 go 17:31:24 🎆🎆 go 🎆🎆 17:31:25 * Go! 17:31:25 * t0xic0der[m]1 is suddenly nervous 17:31:40 (also go, but late) 17:31:52 QA? 17:31:59 can I say it? 17:32:10 coremodule: do it! 17:32:10 say 17:32:12 GO! 17:32:20 Go 17:32:34 #agreed Fedora Linux 36 Final is GO 17:32:34 #info Fedora Linux 36 Final will release on 2022-05-10 17:32:39 wohoo! 17:32:40 weeeeeee 17:32:44 #action bcotton to announce decision 17:32:50 Good 17:32:50 hurray! 17:32:55 Yay! 🎉 17:32:58 Woot! 17:32:59 Yay! Shipit! 17:32:59 #topic Open floor 17:32:59 Anything else we need to discuss before closing? 17:33:00 thanks for all the hard work everyone! 17:33:10 i'm just glad F36 will release before F37 beta does ;-) 17:33:10 thanks everyone really! 17:33:14 🎉 17:33:25 ben :) 17:33:25 yaaay 17:33:26 thanks everyone 17:33:35 #info don't forget to sign up to attend the f36 release party: https://hopin.com/events/fedora-linux-36-release-party/registration 17:33:58 And the release party will be after the release 😁😁😁 17:34:09 🎉 17:34:46 Thanks everyone for all the work they have done for this release 17:34:53 words cannot express how glad i was that i told Marie we should do it the 13th and 14th instead of the 6th and 7th 17:35:13 🙏 17:35:24 well done past bcotton 17:36:08 alright folks, i guess i have an email to send 17:36:15 thank you and i'll see you at the release party! 17:36:17 so in other news, bugs with perl and mysql - how much will that break? :p 17:36:46 Seems with the F36 update to MariaDB, it breaks DBD::MySQL and SSL 17:37:00 but I'm still trying to get my head around it. 17:37:03 adamw++ 17:37:04 YAY Thanks everyone! 17:37:29 bcotton++ 17:37:29 geraldosimiao: Karma for bcotton changed to 15 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:37:36 CRCinAU: well, it'd break openqa for one thing. :P but we can deal with that post-release. i'll take a look if i get time. 17:37:39 #endmeeting