Topic Test planning for F40
by Peter Boy
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
3 months, 2 weeks
LVM configuration change issue - urgent
by Peter Boy
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
4 months