server October 2022

server@lists.fedoraproject.org

7 participants
11 discussions

Federa 35 Server default editor
by Peter Boy 14 Mar '23

14 Mar '23

In Fedora 34 the default editor was nano, for Workstation and also for Server. In my latest default F35 Server installation I noticed vim-default-editor was installed. Did some good soul take pity and bring vim back to us or did something go wrong with my installation? Best Peter

8 25

Server critical path definition proposal
by Adam Williamson 20 Oct '22

20 Oct '22

Hey folks! Just wanted to give a heads-up about this ticket: https://pagure.io/fedora-comps/pull-request/777 that would define a critical path for Server. That would mean updates containing any of those packages or their dependencies would be 'critical path' updates, meaning they have higher requirements to be pushed stable (+2 karma or 14 days waiting, as opposed to +1 karma or 7 days waiting for regular updates), and openQA would test them automatically and they would be blocked from stable if the tests fail. See this devel@ discussion on expanding the critpath definition for background: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… Please chime in if you have any thoughts/concerns/suggestions. Thanks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

2 4

Cockpit 278, and cockpit-podman 55
by Jelle van der Waa 19 Oct '22

19 Oct '22

Happy Wednesday! Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from Cockpit version 278, and cockpit-podman version 55: https://cockpit-project.org/blog/cockpit-278.html Summary: - Metrics: Display individual disk read/write usage - cockpit-podman: Create new pod support - cockpit-podman: Pod CPU, memory, port and volume details Cockpit 278 is available for download here: - source: https://github.com/cockpit-project/cockpit/releases/tag/278 - Fedora 37: https://bodhi.fedoraproject.org/updates/FEDORA-2022-957c7eaa0d - Fedora 36: https://bodhi.fedoraproject.org/updates/FEDORA-2022-614e5cb4e7 cockpit-podman 55 is available for download here: - source: https://github.com/cockpit-project/cockpit-podman/releases/tag/55 - Fedora 37: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d1924d2873 - Fedora 36: https://bodhi.fedoraproject.org/updates/FEDORA-2022-8e6b0d9122

1 0

Call for agenda Items on 2022-10-05 17:00 ==UTC== meeting
by Peter Boy 19 Oct '22

19 Oct '22

The meeting date ========================================================= Fedora Server IRC meeting Wednesday, Oct. 19 17:00 ==UTC== irc.libera.chat #fedora-meeting ========================================================= Please, check your local time using date -d ‘2022-10-19 17:00UTC‘ The agenda includes so far: == Agenda == https://pagure.io/fedora-server/report/Meeting 1. = Follow up actions = 2. = Release 37 Beta testing = #link https://pagure.io/fedora-server/issue/91 Goal: Current status auf further actions 3. = Documentation update Release 37 = #link https://pagure.io/fedora-server/issue/94 Goal: review current status and further action 4. = Server critical path definition proposal = #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or… Goal: Initial discussion how to improve release criteria, test procedures, etc. Please, try to read the thread mentioned above in advance. 5. = Open floor = For any additions or changes, please reply to this email. For an overview about current tasks look at: https://pagure.io/fedora-server/boards/Works%20in%20progress

1 0

Fwd: [Test-Announce] Fedora 37 Candidate RC-1.2 Available Now!
by Adam Williamson 18 Oct '22

18 Oct '22

Hi folks, just a heads-up that the second RC for 37 Final is out now and we need to get through the testing by Thursday. There are a few potential blockers to work through, but so far I kinda suspect we may decide to reject or waive the ones that have arisen, so I still want to treat this as a 'viable' candidate for now and get all the tests run on it. This particularly includes the Active Directory tests (pinging sgallagh, thanks as always...) and testing Cloud on real clouds. The forwarded email has links to the results pages, which have links to the images (including AMIs on the Cloud results page). You can edit results into the wiki pages directly or use `relval report-results` (after `dnf -y install relval`) which is a CLI that edits the pages for you and makes the process slightly less annoying. :D Thanks a lot folks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

[Fedocal] Reminder meeting : Fedora Server WG
by pboy＠fedoraproject.org 18 Oct '22

18 Oct '22

Dear all, You are kindly invited to the meeting: Fedora Server WG on 2022-10-19 from 17:00:00 to 18:00:00 UTC At fedora-meeting(a)irc.libera.chat The meeting will be about: Standing meeting of the Fedora Server Working Group More information available at: [https://pagure.io/fedora-server/report/Meeting](https://pagure.io/fedora-se… Source: https://calendar.fedoraproject.org//meeting/10247/

1 0

Fedora 37 Final status update
by Adam Williamson 15 Oct '22

15 Oct '22

Hi, folks! Just wanted to make sure everyone's aware of the current status with regards to the Fedora 37 release. We are waiting on a couple of key things to build a release candidate: a new glibc build for https://bugzilla.redhat.com/show_bug.cgi?id=2129358 , and improved upstream fixes for the gnome-calendar recurring event bugs. Both of those are being actively worked on and I'm hoping they'll arrive today or tomorrow; as soon as they do, I'll request a candidate compose. In the mean time, it'd be great if folks can test and karma the pending updates for blocker and FE bugs, which are listed on blockerbugs: https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist especially it'd be great to have as much testing as possible of the kernel update. It'd also be great if folks can help fill out the validation matrices for the current compose: https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20221012.n.0… even though we won't ship that compose, it's pretty similar to what we will ship, and it'd be very good to have the tricky tests like Active Directory, unusual storage, and Cloud tests run now just in case there are any lurking issues. And if necessary, we'll be able to transfer results forward to the RC for tests that shouldn't be affected by anything changed in it. Thanks a lot, folks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

Re: Agenda Items on 2022-10-05 17:00 ==UTC== meeting
by mowest＠vivaldi.net 05 Oct '22

05 Oct '22

Wow, I hope you feel better soon, Jason. I'm going to miss part of the meeting, because I'm heading to the doctor to get my leg looked at. I'm in a lot of pain after a bicycle accident last night (my own dumb fault, not with a car). I hoping that surgery isn't needed, and that I just pulled a bunch of muscles and stretched some tendons, but I soon find out. On Wednesday 05 October 2022 11:17:11 AM (-04:00), J Beard wrote: Unfortunately, I’m going to miss today's meeting. I’m recovering from surgery I had on Monday. I completely tore my bicep tendon from my foreman last week. Jason From: Peter Boy <pboy(a)uni-bremen.de> Sent: Wednesday, October 5, 2022 10:14:03 AM To: server(a)lists.fedoraproject.org <server(a)lists.fedoraproject.org> Subject: Agenda Items on 2022-10-05 17:00 ==UTC== meeting The meeting date ========================================================= Fedora Server IRC meeting Wednesday, Oct. 05 17:00 ==UTC== irc.libera.chat #fedora-meeting ========================================================= Please, check your local time using date -d ‘2022-10-05 17:00UTC’ The agenda as agreed upon last meeting: == Agenda == https://pagure.io/fedora-server/report/Meeting 1. = Follow up actions = 2. = Release 37 Beta testing = #link https://pagure.io/fedora-server/issue/91 - Follow up: Who is doing what 3. = Documentation update Release 37 = #link https://pagure.io/fedora-server/issue/94 - Follow up: Current state 4. = Using Ansible to install and configure Wildfly = #link https://pagure.io/fedora-server/issue/60 Goal: Discussion how to proceed further 5. = Open floor = For any additions or changes, please reply to this email. For an overview about current tasks look at: https://pagure.io/fedora-server/boards/Works%20in%20progress Vor an overview about previous meetings: https://docs.fedoraproject.org/en-US/server-working-group/wg-minutes-curren… _______________________________________________ server mailing list -- server(a)lists.fedoraproject.org To unsubscribe send an email to server-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com

1 0

Agenda Items on 2022-10-05 17:00 ==UTC== meeting
by Peter Boy 05 Oct '22

05 Oct '22

The meeting date ========================================================= Fedora Server IRC meeting Wednesday, Oct. 05 17:00 ==UTC== irc.libera.chat #fedora-meeting ========================================================= Please, check your local time using date -d ‘2022-10-05 17:00UTC’ The agenda as agreed upon last meeting: == Agenda == https://pagure.io/fedora-server/report/Meeting 1. = Follow up actions = 2. = Release 37 Beta testing = #link https://pagure.io/fedora-server/issue/91 - Follow up: Who is doing what 3. = Documentation update Release 37 = #link https://pagure.io/fedora-server/issue/94 - Follow up: Current state 4. = Using Ansible to install and configure Wildfly = #link https://pagure.io/fedora-server/issue/60 Goal: Discussion how to proceed further 5. = Open floor = For any additions or changes, please reply to this email. For an overview about current tasks look at: https://pagure.io/fedora-server/boards/Works%20in%20progress Vor an overview about previous meetings: https://docs.fedoraproject.org/en-US/server-working-group/wg-minutes-curren…

2 1

Possible Networking Bug in F37 Server Beta
by mowest＠vivaldi.net 05 Oct '22

05 Oct '22

I may only be at the Fedora Server WG meeting today for a short time, because of a doctor's appointment, so I wanted to mention something that came up when I was reviewing the documentation for Fedora Server Installation and Post Install Tasks. I tested the Fedora Server Standard ISO image install on the following hardware: TOSHIBA product: Satellite C650 v: PSC2EU-001027 Mobo: TOSHIBA model: Portable PC serial: <filter> BIOS: INSYDE v: 1.00 date: 04/01/2011 CPU: Topology: Dual Core model: Intel Core i3-2310M bits: 64 type: MT MCP arch: Sandy Bridge Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Toshiba America Info Systems driver: i915 Network: Device-1: Qualcomm Atheros AR8152 v2.0 Fast Ethernet vendor: Toshiba America Info Systems driver: atl1c Device-2: Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver: rtl8192ce Since, the laptop has a built in wifi adapter, I decided to set up networking during the install using that device. Fedora Server installed without issue, but when I tried to connect to it remotely I could not. - The system had received an internal IP address from my DHCP server. My DHCP server could see the system connected to the network at the address it was assigned. The Fedora Server login prompt correctly displayed the internal IP address that it had been given. - Yet, I could not ssh to the system. Cockpit would not come up when I tried to access Cockpit from my workstation on the same LAN. I was unable to ping the system as well. - However, when I logged into the system directly, I had the correct IP address connected through the wireless adapter, and I could do a "sudo dnf update" without any problems. I tried plugging in an Ethernet cable, which still didn't allow me to connect remotely to the system, until I rebooted. After a reboot, I was able to ssh, connect to Cockpit, and ping the system. However, when I closed the lid of the laptop (putting the system to sleep) and then opened the lid again later, once again coming out of sleep I have all of the same connection issues that I had before. I'm not sure what is happening during sleep that causes the remote connections to be lost. When I run "ip address" it looks the same when I reboot and have the ethernet cable plugged in as when I wake the system from sleep and run the command again. I realize that connecting Fedora Server with wifi is not the most common way to network a server, but I didn't find anything in the documentation that mentioned that wifi connections would not allow remote access. So, I believe this is a bug in Fedora Server 37 Beta, and one that would be good to address before release of Fedora 37.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

server October 2022