See issue https://pagure.io/fedora-server/issue/125
We should discuss and organize 2 topics, I think
a) What do we want to manually test?
====================================
At the very least, we should conduct a "smoke test" of the installation media and also of the most important functions.
- Does it work as expected
- any irregulary warnings or error messages?
- Any SELinux issues?
- Correct screen display (no distortions)?
- Follow the corresponding documentation, if exists, what updates are needed (create ticket for each doc)
Items requiring testing
- full default installation x86
- full RAID installation x86
- network default installation x86
- Create aarch64 SBC runtime image
- Update an existing installation using dnf upgrade plugin (x86)
- Update an existing aarch64 SBC
- Adding virtualization
- Instantiate a Fedora Server VM
- Install systemd-container infrastructure
- Create a systemd system container
- Installing httpd and create a custom website
- Install PostgreSQL and create a test database
- Update an existing database
- Manual tests of IPA (don’t remember the details, @abbra @sgallagh)
Either we should use the general QA WIKI page for Server tests or we may create a specific Server WIKI page for test results?
In the former case we should create a short description for each test to use in the test table.
Maybe we should create a short guide how to use the QA test page for server?
b) What are the potentially critical changes that we should specifically monitor and test?
The list of Change proposals should b e complete now. Someone has to check these.
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
We have new additional business for our meeting today.
We had a long discussion about arm-image-installer and various issues with maintaining LVM devices.
As it has now become clear, all this is the result of an unannounced silent change in LVM, which has led to a drastically different behavior of the software.
See https://bugzilla.redhat.com/show_bug.cgi?id=2258764
Obviously with F38 LVM changed from searching all devices with pvs and vgscan to searching just devices listed in /etc/devices/system.devices it it exists. Even worse, the update using dnf upgrade plugin create that directory, but not the file, whereas a new installation also creates the file. This gives us two fundamentally different behaviors of the same release status.
In my opinion, this change would have required a change proposal and also a detailed explanation in the release notes. Unfortunately, that approach has led to considerable unnecessary and wasted extra work for many people.
Anyway, now we have to find a solution. The LVM behavior is apparently controlled by a parameter that currently limits the search for VGs to devices listed in the file in question. I suggest to change the behavior to search on all devices via Change Proposal, and thus restore the behavior of F37 and earlier.
There seems to be an option use_devicesfile in lvm.conf. Details in the bug report above.
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
Just updated another article:
Creating a virtual machine using Fedora Server Edition disk image
https://docs.fedoraproject.org/en-US/fedora-server/virtualization/vm-instal…
The update should be online about 15 mins past next hour.
The modifications are minimal, nevertheless review appreciated.
Meet you later today at our meeting.
Peter
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
Hi folks,
I’ve just updated two virtualization articles to F39:
Introduction
(https://docs.fedoraproject.org/en-US/fedora-server/virtualization/index.html)
Adding Virtualization Support
(https://docs.fedoraproject.org/en-US/fedora-server/virtualization/installat…)
Both are more or less minor modifications, but a review is nevertheless appreciated.
For the letter, there is still the issue, that systemd-resolved split dns neither works with libvirt virtual interface virbr0 out of the box nor the manual post-boot fix works as expected (https://docs.fedoraproject.org/en-US/fedora-server/virtualization/installat…) The resolvectl commands stopped working with F35.
The problem is, that the commands
resolvectl dns virbr0 192.168.122.1
resolvectl domain virbr0 example.lan
as described in the article set the DNS and Domain for interface virbr0, but leave the "Current Scope“ as none (instead of DNS and LLMNR/IPv4 )
If someone knows a solution or can evaluate the issue …
Best
Peter
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
I wish us all a happy new year!
And a year as productive as the last one.
Our upcoming first meeting this year will be held on
===========================================================
Fedora Server IRC meeting Wednesday, Jan 17 18:00 ==UTC==
irc.libera.chat #fedora-meeting
===========================================================
Please, check your local time using date -d '2024-01-17 18:00UTC'
==== Agenda ====
#link https://pagure.io/fedora-server/report/Meeting
To be able to discuss all topics on the agenda and to prevent us from repeatedly putting off topics that have not been dealt with, we should set time limits for the individual items on the agenda. If we need more time, we should continue on the mailing list.
1. === Follow up actions and announcements ===
== Proposal for meeting planning ==
January has 5 Wednesdays. We should use the Wednesday in 14 days (January 31) for an _additional_ meeting to discuss and make required decisions soon.
2. === Add module cockpit-navigator to default Installation ===
#link https://pagure.io/fedora-server/issue/111
3. === Issue 114: LLMNR should be disabled in systemd-resolved in f39
#link https://pagure.io/fedora-server/issue/114
4. === Aarch64 SBC Installation bug on Fedora Server
#link https://bugzilla.redhat.com/show_bug.cgi?id=2246871
5. === Test planning for F40 ===
#link https://pagure.io/fedora-server/issue/125
6. === Work program and goals for F40 ===
Previous discussion: Fedora Server goal(s) for F39
#link https://pagure.io/fedora-server/issue/102
7. === 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
===== Pending topics for the upcoming meetings =====
In no particular order:
=== Revisiting Fedora Server release criteria
#link https://pagure.io/fedora-server/issue/61
=== Revisiting Server installation media naming convention
=== Using Ansible to install and configure Wildfly
#link https://pagure.io/fedora-server/issue/60
=== Review installation media
#link https://pagure.io/fedora-server/issue/88
=== A "story" for each release
https://pagure.io/fedora-server/issue/101
=== F39 Work Project: Fedora Server on (ARM) SBC
#link https://pagure.io/fedora-server/issue/108
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast