17:00:33 #startmeeting fedora-server 17:00:33 Meeting started Wed Sep 7 17:00:33 2022 UTC. 17:00:33 This meeting is logged and archived in a public location. 17:00:33 The chair is pboy. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 17:00:33 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:34 The meeting name has been set to 'fedora-server' 17:00:43 #topic Welcome / roll call 17:00:52 Welcome to our Server WG IRC meeting today! 17:01:01 Please, everybody who is lurking, say either .hello2 or .hello 17:01:09 I’ll post the agenda in a few minutes 17:02:06 .hello2 17:02:07 cooltshirtguy: cooltshirtguy 'Jason Beard' 17:02:32 Welcome cooltshirtguy 17:03:15 thanks. I hope your doing good 17:03:48 Yes, after an internet breakdown the last 2 days everything is fine again. 17:04:53 That was a hard time. I didn't know how much I'm used to use the internet. I couldn't do nearly anything. 17:05:10 2 days with no internet. I wouldnt know what to do 17:05:17 hahah 17:06:13 Hm, we are not too many, today. Let's wait another 5 mins 17:06:20 ok 17:12:32 Well, I think we have to postpone everything to the next meeting. 17:12:41 understood 17:12:49 Do you have anything we should discuss now? 17:13:28 nope 17:13:51 OK, just an announcemnt for the books: 17:14:10 #info Update to my mail: Thanks to nirik we have a Server VM image in F37 and in Rawhide. 17:14:23 Kevin (nirik) processed the PR and someone, I don’t know how, but probably nirik as well, wrote the integration script for the build system. 17:14:23 nice 17:14:36 #link https://koji.fedoraproject.org/koji/taskinfo?taskID=91733076 17:14:37 well, except... 17:14:46 it failed on ppc64le and aarch64. ;( 17:15:06 Yes, but I think I know the cause. 17:15:07 and it didn't quite make the beta RC. ;( 17:15:18 yeah, hopefully it's an easy fix. 17:15:28 Can I do another PR or is it better to do nothing? 17:16:05 And do we have a chance for the next RC? 17:16:19 another PR with a fix would be great. well, or two... one for rawhide, one f37 17:16:27 if there is one. 17:17:10 Yes, aarch64 is a bit stricter with the filesystem type. This seems to be the cause. 17:18:09 Anyway, I’m really happy now, after a lot of work I had done. 17:18:30 Again, many thanks to nirik. 17:18:37 And to sgallagh for support on the not so easy way to get the kickstart file done. 17:18:51 thanks for working on it pboy! 17:19:10 pboy++ 17:19:10 sgallagh: Karma for pboy changed to 1 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:20:01 thanks! It was my first technical contrib after all the documentation. 17:20:43 And it is the first notiable change for Fedora Server after a long time. 17:21:03 hello, folks 17:21:15 sorry I'm late, something came up 17:21:22 Welcome eseyman 17:21:53 Now we have the quorum, and I think we can start - and should do so! 17:22:13 #topic Agenda 17:22:22 #link https://pagure.io/fedora-server/report/Meeting 17:22:29 #info Follow up actions 17:22:37 #info Release 37 Beta testing 17:22:44 #info Server VM status and the way forward 17:22:52 #info I Work planning for the next 6 months 17:22:58 #info Open Floor 17:23:06 Any additional topic / issue / comment ? 17:23:33 I see none 17:23:36 not for me 17:23:43 nope 17:23:46 #topic Follow up actions 17:23:54 #info Currently no open actions 17:24:03 #info Still to do: final editing of the technical specifications as decided last meeting. 17:24:22 Does anyone has anything to add here? 17:25:05 #topic Release 37 Beta testing 17:25:14 #link https://pagure.io/fedora-server/issue/91 17:25:23 #info Fedora 37 Candidate Beta-1.5 Available 17:25:33 #link https://fedoraproject.org/wiki/Test_Results:Fedora_37_Beta_1.5_Server 17:26:17 I think, there are at least 4 subtopics: 17:26:26 1. Current state of the Software Raid installation issue 17:26:34 2. how to deal with bug reports found a long time ago and unprocessed since then 17:26:41 3. How to systematize testing 17:26:53 4. Where are there additional testing needs to automated testing? 17:27:26 Any additional ideas? 17:28:22 that's already a lot to talk about 17:28:34 Indeed. :-) 17:28:42 So let's start with: 17:28:51 1. Current state of the Software Raid installation issue 17:29:10 It was accepted as a blocker bug, but is it really? 17:29:21 Didn’t see it in bcottons mails. 17:29:31 #link http://qa.fedoraproject.org/blockerbugs/current 17:29:58 I'm wondering, what to do. 17:31:17 adamw Are you online by any chance? 17:31:26 One easy win is to document the current state of affairs 17:31:38 pboy: it's a final blocker, not a beta one 17:31:45 https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist 17:32:05 (I think? what is the bug number?) 17:32:35 people who want to use software raid should be told upfront that it works or doesn't work 17:33:24 nirik https://bugzilla.redhat.com/show_bug.cgi?id=2088113 17:33:44 yeah, final blocker 17:34:16 OK, very good. Well, I've still to learn the fine details of fedora universe. :-) 17:34:27 so this is only bios boot? 17:35:28 yes, efi did never work with custom, but does work with advanced config (that blivi... I never can remeber) 17:35:53 well, efi has a different problem I guess... the efi partition can only be in one place. 17:35:59 anyhow, sorry for sidetracking. 17:36:56 Yes,anconda resolves that by making it a raid partition. It work with Fedora, but probably with nothing else. 17:37:51 I think, we have to resolve that in a next step, F38 of F39 17:38:54 My biggest concern with this bug has been taken care of. 17:39:03 I will continue to test the installation and comment on the bug. 17:39:29 I've already set up a specific test environment in my home lab 17:39:50 Anything elso to that sub topic? 17:40:07 nope 17:40:29 OK, let's forward to the next one: 17:40:41 2. how to deal with bug reports found a long time ago and unprocessed since then 17:41:08 Specifically it is: 17:41:23 #link https://bugzilla.redhat.com/show_bug.cgi?id=1900869 17:41:41 #link https://bugzilla.redhat.com/show_bug.cgi?id=1900888 17:42:23 The latter is especially bad. you have to deactivate SELinux and must not forget to activate it again afterwards 17:42:50 What can we do about those 2 years old bugs? 17:44:14 humm... 17:44:56 Me either. :-) 17:45:53 I think I will bring to the weekly QA meeting next Monday. Maybe, we can get some advice there. 17:46:32 Maybe, we should first discuss the 4. subtopic: 17:46:44 4. Where are there additional testing needs to automated testing? 17:47:26 It means, we should study the change list for suspicious items. 17:47:54 dns, dhcp and ldap seems like quick wins 17:49:13 Yes, with dns / systemd-resolved there is another longstanding but. Split DNS doesn't work with virtual interfaces, specifically libvirt, out default virtualization 17:49:38 It did work some releases ago. 17:50:49 Maybe the best is, to start a mailing list thread about additional test items? 17:51:50 sounds like a place to start 17:52:04 #agreed We start a thread on the mailing list about additional needs for testing. 17:52:36 I think, we can switch to the next topic? 17:52:54 #topic Server VM status and the way forward 17:53:21 I think, everything is said the the beginning. So we can skip to the next? 17:53:33 yes 17:53:46 #topic Work planning for the next 6 months 17:53:54 #link https://pagure.io/fedora-server/boards/Works%20in%20progress 17:54:19 I think, we have 2 larger projects: 17:54:39 a) review & extend our release criteria 17:54:48 b) review our installation media 17:55:26 a) is probably rather boring and b) is rather complicated. 17:55:43 yes 17:56:05 Any idea what to do? 17:57:22 not really, pick one and move forward? 17:58:45 Yeah. So I think we should start with the release criteria and probably as a more interesting project expand our Ansible project. 17:59:08 So we have 2 in parallel, that should be possible. 17:59:30 Eseyman what about your Ansible project ideas? 18:00:52 well, my idea was to build the SBC reference list and create Ansible roles based on that 18:01:25 I did spend part of my vacation writing the dnsmasq one and it's almost complete 18:01:41 I'll probably finish this weekend 18:02:26 so release criteria should come first 18:02:38 That's a lot of progress! 18:03:15 Yeah, release criteria is somewhat dry, but important. 18:03:39 it would make a lot more things simpler to do 18:03:54 I see, our time is up. Let's continue with this topic text meeting. 18:04:15 I would close, if nothing else is to talk about? 18:04:19 nope 18:04:41 ok. Bye then and see you in 2 weeks and on mailing list. 18:04:49 see you, folks 18:04:56 #endmeeting