15:00:03 <adamw> #startmeeting Fedora QA Meeting
15:00:03 <zodbot> Meeting started Mon Oct 26 15:00:03 2020 UTC.
15:00:03 <zodbot> This meeting is logged and archived in a public location.
15:00:03 <zodbot> The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:03 <zodbot> The meeting name has been set to 'fedora_qa_meeting'
15:00:06 <adamw> #meetingname fedora-qa
15:00:06 <zodbot> The meeting name has been set to 'fedora-qa'
15:00:10 <adamw> #topic Roll call
15:00:12 <adamw> morning morning everyoe
15:00:17 <adamw> also everyone
15:00:51 <Southern_Gentlem> .hello jbwillia
15:00:52 <zodbot> Southern_Gentlem: jbwillia 'Ben Williams' <vaioof@gmail.com>
15:02:59 <adamw> well, turnout is great today
15:03:09 <adamw> is there a holiday and i wasn't invited?
15:03:14 <bcotton> .hello2
15:03:15 <zodbot> bcotton: bcotton 'Ben Cotton' <bcotton@redhat.com>
15:03:39 <adamw> oh, great, BEN's here *eyeroll*
15:04:21 <bcotton> next time you should complain about low turnout more specifically
15:05:06 <cmurf> .hello chrismurphy
15:05:07 <zodbot> cmurf: chrismurphy 'Chris Murphy' <bugzilla@colorremedies.com>
15:05:46 <bcotton> by my reckoning, this meeting is now 67% Ben
15:06:11 <adamw> you may need to check your calculator
15:06:23 * cmurf can make up for any lack of silliness
15:06:34 <adamw> cmurf: that does not seem to be a risk of qa meetings
15:06:41 <bcotton> curse you, matrix-irc connection!
15:06:48 <cmurf> dammit i forgot to login with my parody account
15:07:01 <bcotton> it delayed my message on purpose just to make me look dumb. as if i need the help
15:07:29 <adamw> "look" dumb
15:07:31 <tflink> i see we're off to an interesting start :)
15:07:57 <cmurf> bcotton are your men on the right pills?
15:09:07 <cmurf> wait where are your minions?
15:09:11 <adamw> well, i guess we have three people and ben now
15:09:14 <adamw> we could go ahead
15:10:40 <adamw> #topic Previous meeting follow-up
15:11:19 <adamw> "coremodule to finalize the IoT criteria merge, taking into account any further feedback, and put it into 'production'"
15:11:25 <adamw> .fire coremodule
15:11:28 <zodbot> adamw fires coremodule
15:11:38 * kparal arrives late
15:12:14 <adamw> #info "coremodule to finalize the IoT criteria merge, taking into account any further feedback, and put it into 'production'" - this was done, see https://pagure.io/fedora-qa/issue/622
15:12:23 <adamw> any other follow up from last time?
15:14:13 <adamw> okay then
15:14:21 <adamw> #topic Fedora 33 status and actions (Secure Boot key issue?)
15:14:35 <adamw> #info f33 was signed off Thursday and will release tomorrow
15:14:42 * kparal pokes lruzicka lbrabec_ frantisekz
15:14:45 <adamw> #agreed many thanks to all who contributed to validation testing
15:14:57 <kparal> \o/
15:15:03 <adamw> i believe this is the first cycle since i joined RH in which i did exactly no manual validation tests
15:15:09 <adamw> Project Coconut is real :P
15:15:15 <cmurf> haha
15:15:25 <bcotton> #info adamw is unnecessary now
15:15:30 <adamw> gloriously unnecessary!
15:15:31 <cmurf> the coconuts have be redirected to everyone else's heads?
15:15:40 <adamw> you know, you just need someone else to pick up after the robots
15:15:41 <cmurf> ^falling
15:15:47 * kparal grumbles
15:16:49 <cmurf> what's got kparal grumbly?
15:17:09 <adamw> #info the bug about images being signed with a pre-BootHole Secure Boot key and hence not booting in Secure Boot mode if those keys are revoked was not fixed: https://bugzilla.redhat.com/show_bug.cgi?id=1883609
15:18:05 <kparal> cmurf: the fact that project coconut hasn't been activated for me
15:18:13 <Southern_Gentlem> so shouldnt that be a beta blocker for f34
15:18:19 <adamw> so the F33 images are signed with an older key, and as the F33 cycle goes on there is a non-zero chance that Microsoft or other OS vendors or OEMs may send out updates that revoke the key they're signed with. Microsoft is supposedly committed to not doing this until q2 2021, which is close to f34 release.
15:18:28 <adamw> Southern_Gentlem: oh, yeah, it probably should. or at least a final one.
15:18:59 <adamw> kparal: you just need to build your own automated test system and monitor it continuously :P
15:19:36 <adamw> at go/no-go and in the tickets we've talked about the possibility of doing some kind of re-spin / point release for f33 if the key issue becomes a big problem
15:20:02 <adamw> #info a point release / re-signed re-spin of Fedora 33 is a possibility if the key signing issue becomes a big problem
15:20:04 <kparal> adamw: my robots are talking back to me
15:20:10 <adamw> I'm not sure if we have any concerns about this from a QA perspective
15:20:13 <adamw> kparal: haha, they do that
15:20:23 <Southern_Gentlem> after tomorrow the respins Sig will be testing respinning the lives
15:20:48 <bcotton> adamw: i have a concern for this from a QA perspective
15:20:57 <adamw> i think the validation process is smooth enough at this point that we could probably manage to test a respin without too much trouble, of course the more changed it is from the original f33 release the more likely we are to find bugs and spend time on that
15:20:59 <cmurf> there's competing issues: not pushing the revocation means systems are BootHole vulnerable, pushing the revocation takes up space in a resource limited NVRAM location
15:21:45 <adamw> cmurf: that seems kinda out of scope for our meeting, it's not up to us to worry about whether to ship the revocation or not in anything. for us it's prudent to just assume that it is going to happen at least to some people at some point.
15:23:22 <cmurf> so what's on the table for a respin? just the fedora repo plus an updated shim? or fedora + updates repos?
15:24:08 <adamw> i don't think anyone knows.
15:24:11 <bcotton> that's my concern. i'd like to know what QA likes
15:24:30 <bcotton> we'll have to figure it out, once we know more about the timing, etc
15:24:38 <Southern_Gentlem> 1) is less testing 2) for the community would make more sense
15:25:19 <bcotton> in an ideal world, we'd have the new images be as up-to-date as possible, but would potentially mean a freeze, which would present other complications
15:25:41 <bcotton> so i'd like to figure out what's desired and then figure out how close we can get tot hat
15:25:47 <Southern_Gentlem> 2) could have more breakage
15:25:52 <cmurf> guess it also depends on where we are in F34 cycle too
15:25:52 <adamw> yeah. 1) would definitely substantially increase the chance that it's shippable right away.
15:26:02 <adamw> from a QA perspective i think 1) is inarguably preferable
15:26:06 <cmurf> is it possible to do two freezes or even non-overlapping freezes
15:26:15 <adamw> from a QA perspective the ideal state of affairs is that we never release anything to anyone. :P
15:26:29 <adamw> cmurf: technically, sure. practically, could be confusing, i guess.
15:26:58 <Southern_Gentlem> The Respins Sig will gladly help in anyway we can
15:29:09 <adamw> #info for QA purposes, a straight respin of F33 release images with resigned bootloader but no other changes would be significantly less work than an updated point release
15:29:13 <adamw> any other thoughts on this?
15:31:03 <adamw> so aside from that, i don't have any pressing f33-related actions
15:31:09 <adamw> common bugs needs updating, i'll work on that today
15:31:19 <cmurf> if it's just shim, a specific test of "make media try to boot, no need to install" may help get more testing sooner
15:31:22 <adamw> oh, lruzicka already made a start
15:31:29 <cmurf> s/may/would/
15:31:30 <adamw> #info lruzicka has already started updating F33 common bugs
15:31:41 <adamw> #action adamw to do any further common bugs updating required
15:31:59 <adamw> cmurf: we'd want to test that an installed system booted too just to be sure, but yeah, that's all it would really need
15:33:24 <adamw> anything else on f33?
15:34:12 <adamw> #topic Test Day / community event status
15:34:16 <adamw> sumantro: around?
15:35:08 <cmurf> kernel 5.9 test week this week
15:36:10 <cmurf> oh and anyone who has done btrfs testing who hasn't claimed the Btrfs testing badge, lemme know
15:36:50 <adamw> #info if you've done any btrfs testing but not got the badge for it, poke cmurf and he'll give it to you
15:37:07 <adamw> #info kernel 5.9 test week is this week: https://fedoraproject.org/wiki/Test_Day:2020-10-26_Kernel_5.9_Test_Week
15:39:25 <adamw> okey dokey
15:39:27 <adamw> #topic Open floor
15:39:30 <adamw> any other business, folks?
15:39:47 <kparal> nothing here
15:40:06 <tflink> I don't have anything
15:40:37 <adamw> well why not goddamnit?!
15:41:07 <tflink> because robots?
15:41:09 <cmurf> get that guy more coffee!
15:41:45 <adamw> alrighty then, i guess we're done here
15:42:15 <adamw> thanks for coming, folks
15:43:08 <kparal> thanks everyone
15:43:14 <adamw> great job on f33, again
15:43:39 <cmurf> thanks!
15:43:50 <adamw> #endmeeting