15:00:23 #startmeeting Fedora QA meeting 15:00:23 Meeting started Mon Jun 7 15:00:23 2021 UTC. 15:00:23 This meeting is logged and archived in a public location. 15:00:23 The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:23 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:23 The meeting name has been set to 'fedora_qa_meeting' 15:00:41 it works! 15:00:47 #meetingname fedora-qa 15:00:47 The meeting name has been set to 'fedora-qa' 15:00:53 #topic Roll Call 15:01:04 ahoyhoy folks, who's around for meeting fun? 15:01:23 * coremodule is here, unregistered with Libera so wondering if my messages are actually getting out... 15:01:28 hex 15:01:30 hey 15:01:32 i see ya, coremodule 15:01:39 thank you! 15:01:40 hi andi 15:01:49 .hello andilinux 15:01:50 andi89gi: andilinux 'Karsten Andreas Artz' 15:03:47 .hello chrismurphy 15:03:48 cmurf[m]: chrismurphy 'Chris Murphy' 15:04:37 btw, did no-one catch my deliberate mistake in the meeting announcement? :D 15:04:43 I did!! 15:04:48 lol 15:05:05 well i wish you'd said :P 15:05:46 I mean, I noticed it 30 minutes ago when I logged on.. but then I wondered if maybe you were trying to start a mass-return from exodus back to freenode... so i went with it 15:06:16 * kparal is here 15:06:18 sorry, got distracted 15:06:20 Hello, is this the correct chat for meeting? 15:06:22 it is 15:06:28 thank god 15:06:31 the meeting announcement was just a test 15:07:16 gotta keep you on your toes 15:07:25 okay, so let's get goin' 15:07:29 #topic Previous meeting follow-up 15:07:36 on a serious note, I couldn't find the announcement. not sure if I managed to delete by accident or if others hit the same issue 15:08:11 tfli: huh. it definitely got back to me as a test-announce mail... 15:08:27 tflink: I see it 15:08:40 https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org/thread/BBDPGXLSC4PICIWYCNQRG4HTGYPNZMEE/ 15:08:41 ok, I must have deleted it by accident or something like that 15:08:54 which bothers me but is very off topic 15:09:18 okely dokely 15:09:36 #info "adamw to create F35 release criteria pages" - I did that, they are up now 15:09:42 anyone have any other follow-up from last week? 15:11:46 alrighty 15:11:55 #topic Chat status: Freenode, Libera.chat, Matrix, oh my 15:12:17 now let's hope the channel isn't automatically shut down by a keyword scan for "Freenode"...:P 15:12:41 that would be funny in a horrible way 15:13:06 aaand we lost adam and kamil 15:13:17 but seriously folks! this has obviously caused a bit of disruption lately 15:13:59 for anyone who somehow is here but isn't aware of it yet, there was a rather nasty fallout between the person who owns the "freenode" intellectual property and the people who were running the freenode irc network, which led to the latter walking out and founding a new network, which is what we're on now - libera.chat. 15:15:03 for various reasons, fedora decided to go with the libera.chat side of this fallout, so at this point more or less everything fedora IRC-y is moved to libera.chat, including this channel, #fedora-qa , and #fedora-blocker-review . 15:15:16 basically anything that we previously did on freenode we will now be doing here, in the same-named room. 15:15:46 #info Fedora has moved all official IRC usage from freenode to libera.chat. all channel names etc. stay the same. 15:16:59 for folks using Matrix, there are folks from Fedora, Libera.chat and Matrix all working hard to get bridging between Libera.chat and Matrix working well. I believe it's still a bit of a work in progress but it is mostly working at this point (I am running this meeting from Matrix) 15:17:15 kparal wrote a handy blog post about how you can set it up here: https://kparal.wordpress.com/2021/06/01/connecting-to-libera-chat-through-matrix/ 15:17:47 Disclaimer: I had no idea what I was doing, just mashing keys on the keyboard 15:17:56 #info Matrix<->Libera.chat bridging is still a bit of a work in progress, but mostly works, see kparal's blog post for some tips 15:18:02 kparal: like usual then 15:18:06 adamw: I don't know if it showed up from your end, but you and kamil did disconnect and reconnect earlier in the meeting 15:18:18 I am using Matrix, too, but I am not sure how I recognize which birdge I am using with what service. LiberaChat Bridge status has invited me to join, but I was not shure if this channel is bridged or not. 15:18:19 Right, that's a permanent disclaimer :-) 15:18:23 I SAID IT WORKS PERFECTLY 15:18:33 Well, IMO it's okay that we have switched to libera.chat 15:18:41 lruzicka: `!listrooms` in chat with appservice should tell you 15:19:13 so, any questions/concerns/ideas/issues on this part so far? 15:19:57 Hmm, this room is not on matrix.org, but on matrix.scrye.com (Kevin's server?) 15:20:07 !listrooms 15:20:21 coremodule: not here, read my blogpost :-) 15:20:22 !mushrooms 15:20:28 !99redluftballoons 15:21:28 coremodule: Nina Hagen 15:21:40 kparal: i don't think that's what the "room ID" means 15:22:00 i think that has nirik's address in it because he created it or owns it, or something 15:22:13 not 100% sure, though... 15:22:28 ¯\_(ツ)_/¯ 15:22:30 nirik: is this where the insurrection begins? :D 15:22:41 * nirik looks up 15:23:16 whats the question? 15:23:31 oh, that. 15:23:41 from the matrix spec: "There is exactly one room ID for each room. Whilst the room ID does contain a domain, it is simply for globally namespacing room IDs. The room does NOT reside on the domain specified." 15:23:50 long story short, it turned into a joke mostly 15:23:59 why this room looks like it's on matrix.scrye.com 15:24:01 it's cosmetic. :) 15:24:08 I upgraded the room last. 15:24:18 kparal: you owe me a beer 15:25:33 alrighty 15:25:54 * kparal suggests that all future rooms are created with @beer.forever suffix 15:26:13 @beer.and.bacon would be acceptable as well 15:26:24 so, also worth noting that going forward Fedora is still working on setting up our own matrix homeserver, and once that is set up, we could choose to make the matrix rooms 'native' and have IRC bridged 15:26:39 whichever way around it happens, we'll at least have official fedoraproject.org matrix rooms 15:27:07 for now i've updated the wiki pages to refer to libera.chat not freenode; if anyone's aware of any other documentation etc. that needs updating, please either just do so or let me know, thanks :D 15:27:41 #info once Fedora's official Matrix homeserver is up and running we will have official QA-y rooms there, whether they or IRC will be the 'primary' location is still up for discussion 15:28:53 adamw: where is the discussion happening? 15:29:12 we've kicked it around here and on test@ a few times i think 15:29:25 at present i think it's kinda waiting on the homeserver to appear 15:29:36 but if you want to bring it up again, feel free :D 15:32:01 so if everyone's up to speed on that kerfuffle, we'll move on 15:32:07 btw i cannot send to #fedora-qa on the old network, apparently, so if anyone can and there appears to be anyone there who doesn't know about the move, please let them know 15:32:33 (but probably without saying 'freenode' or you might get abducted by MIBs) 15:32:41 I wonder if it's non-posting 15:32:41 er, without saying libera, rather. 15:32:50 maybe 15:32:51 i didn't dig into why 15:32:57 #topic Fedora 35 status 15:33:25 so, we lost Rawhide composes for a week due to a builder upgrade, but they seem to be back now. they're mostly working, some miscellaneous bugs 15:33:45 #info Rawhide composes stopped working for a week due to a problem caused by a builder upgrade, it's fixed now and composes are back; they are mostly working 15:33:56 * nirik is pretty surprised at that... since I didn't do anything to fix the qemu thing. 15:34:01 i'm not aware of any major issues atm, anyone got anything to flag up? 15:36:13 It's pretty suspicious when a thing reverts to order. 15:36:35 yeah, me too. 15:36:41 nirik: oh, i thought you must've fixed something. huh. 15:36:41 well, we definitely got two composes 🤔 15:36:42 i don't see a new qemu build either 15:38:11 sry had a crash with Fedora Kinoite 15:38:27 .hello andilinux 15:38:28 andi89gi: andilinux 'Karsten Andreas Artz' 15:39:12 so... I did update/reboot things last week to make all the builders have the same kernel... 15:39:26 andi: hi again 15:39:26 5.12.8 15:39:38 so perhaps there was a change between 5.12.7 and 5.12.8 15:39:48 well, whatever happened, it works. don't touch anything ever again. :D 15:39:54 i guess we'll have to update the ticket 15:40:13 adamw: hey 15:40:28 * nirik can do that 15:40:45 alrighty, sounds like there aren't any other concerns around f35 atm 15:40:57 we'd better do a Change walkthrough sometime soon, i'll have to schedule it for the next meeting 15:41:05 #topic Test Day / community event status 15:41:08 sumantro: around? 15:41:33 oh hmm, i just noticed zodbot isn't responding to topic changes... 15:42:42 not sure if other commands are working. guess we'll find out at the end :/ 15:42:43 it's responding for me 15:42:55 I see the topic changes, rather 15:43:08 yeah, working fine here. 15:43:21 oh huh. i'm not seeing them. that's odd 15:43:31 I don't think topic is synced over the matrix bridge 15:43:54 no, but i should get the message from zodbot saying the topic changed, shouldn't i? 15:44:47 anyhoo 15:45:08 i don't see much on the community event front this week 15:45:46 #info not much happening here ATM, we will wait to hear from sumantro next time 15:45:49 #topic Open floor 15:45:52 any other business, folks? 15:46:35 nope 15:47:03 ah, peace and quiet 15:47:42 oh, update gating seems to be going okay, i'm working on a few enhancements to make the experience a bit less bumpy for packagers 15:50:09 oh... i actually had something1 15:50:43 oooh! 15:51:10 In the past, the container sig would test containers and then ask releng to upload them to quay.io and dockerhub and such... but the container sig is pretty inactive now, so no one is doing that. Is that something anyone in QA would be willing/like/able to do? 15:52:28 hmm, seems like kind of a significant responsibility 15:52:35 nirik: What's up with container sig? 15:52:39 this is for the post-release nightly builds? 15:52:41 how often are the containers updated? 15:52:46 adamw: yes 15:53:01 daily 15:54:20 is any of the container test automation stuff still running? 15:55:49 I'm not sure. :) 15:56:21 openQA tests the Cloud and CoreOS nightly composes 15:56:25 including running the old autocloud tests on Cloud images 15:56:56 F34 Cloud compose images are still totally broken, btw, they do not boot, neither nirik nor i could figure out why not 15:57:28 adamw: I thought they magically started working? 15:57:40 and... f34 container dailies are failing to compose 15:57:56 as are f33 15:57:59 i kinda feel like this should still be a 'container sig' thing, like if someone wants to help out, they should do it by joining/reviving the container sig... 15:58:00 whee 15:58:15 wait what compose name is this 15:58:27 oh, we have an actual Fedora-Container 15:58:51 how does that differ from Fedora-Cloud ? 15:59:35 Cloud is a cloud/qcow2/raw image, container is a... container? that you would pull with docker or podman 15:59:44 ah right. okay. 15:59:47 ApplianceError: Image status is FAILED: 'Thread' object has no attribute 'isAlive' 15:59:50 fun. ;( 16:00:05 that sounds vaguely familiar 16:00:13 https://github.com/autocracy/python-ipy/pull/69#issuecomment-645718498 16:00:18 it does. I think i fixed it once before 16:01:05 alright, well, that's time... 16:02:06 #info container SIG has gone inactive and so no-one is testing new container composes and requesting they be pushed out to container repositories any more; if anyone is interested in getting that started again please apply to nirik for details 16:03:25 okay folks, thanks for coming 16:03:39 thank you for the updates :) 16:04:34 #endmeeting