I just had a quick look on / test of Fedora Server 36 (rawhide 22-02-18).
- Installation of DVD went smooth and ssh login via administrative user worked fine
- Before I even did anything I noticed a SELinux ACE (SELinux prevents 20-chrony-dhcp from accessing file enp1s0.sources with create access) which then appeared repeatedly several times.
Didn't cause any noticeable problems, but makes an ==untrustworthy impression== of the whole distribution when we not even have our highly praised security system under control.
- Tried to install a system-nspawn mockup container without success. Couldn’t boot the container, got:
Welcome to Fedora Linux 36 (Thirty Six Prerelease)!
Failed to load BPF object: Operation not permitted
BPF LSM hook not enabled in the kernel, LSM BPF not supported
Queued start job for default target graphical.target.
Using headless server, wondering a bit about graphical target.
I got a login prompt, but after typing in the credentials the prompt was just repeated, no working login.
Starting it as system service produced the same SELinux bug that I've reported for years (since about F31 or so). Another indication that we are not in control of our security system.
Unfortunately, I’m too stupid to understand how to enter something into our QA tracking system (apart from a bug report that probably won't fare any better than the ones already there).
Has anyone else tried the rawhide pre-release version?
It's taken more time than I had anticipated but I have finally reviewed
the "Install a F35 VM using Cockpit" page of our user documentation.
My first issue is with the sentence "If there is no entry Virtual
Machines the admin missed to install the cockpit-machines module when
installing the virtualization support. Select Applications further down
and then Machines for installation.".
My cockpit installation did not have the "Virtual Machines" menu option
nor did I have the option to install cockpit modules. I could initially
only remove installed modules. Coming back to this days later, I now see
all cockpit modules, with the ability to install those I don't have. Is
this a known issue or have I done this wrong?
The _images/virtualization-vm-install-fedoraserver-cockpit-020.png image
does not match the form I get on F35. I have a "Connection" option which
gives me the choice between "System" and "Session". This is not
reflected in the image.
The documentation later states "After a test of the installation media
the well known installation process begins. You may select Expand at the
right top to increase readability". In my case, I HAD to click on
'Expand' for the VNC console to register my keystrokes.
In the "Optional post-installation tasks" section, the first task is
titled "Get rid of nano as default editor". I feel "Making vim the
default editor" better reflects the contents of this section. I would
also recommend replacing the command by "dnf install --allowerasing
vim-default-editor" which simplifies the task.
Excuse my ignorance, but I'm just wondering what sense the regular rawhide "compose check reports" make. Who processes this information?
E.g. in today's report "Fedora-Rawhide-20220224.n.1 compose check report" on devel(a)lists.fedoraproject.org I find under New OpenQA failures
ID: 1146980 Test: aarch64 Server-dvd-iso base_reboot_unmount@uefi
and about 17 other failure entries.
Who cares about that? Or is not necessary to take care of it?
The meeting will take place
Fedora Server IRC meeting Wednesday, March 02 17:00 ==UTC==
Please, check your local time using date -d ‚2022-03-02 17:00UTC‘
So far we have according to our plannings the following
== Agenda ==
1. = Follow up actions =
2. = Check F36 changes and known issues - final pass =
Goal: final determination of critical changes
Please add your findings as comment to the ticket!
3. = Specifying F36 manual test requirements - final pass =
Goal: final determination of of manual tests and who takes which test
Please add your options as comment to the ticket!
4. = Review current Fedora Server Technical Specification – second pass =
As agreed I created a first draft of an updated specification on hackmd.io
Proposal for the thematic structure of the discussion.
a. General remarks
b. Discussion of „supported services“ as part of Fedora Server ( sec. 4 & 4.4)
c. Discussion of the requirements for support using Ansible (sec. 4.1
d. Discussion of a possible recourse to Ansible Linux system roles (https://linux-system-roles.github.io/)
e. Agreement about next steps
Obviously we will not be able to discuss all of the subtopics but have to continue next meeting.
4. = Open floor =
For any additions or changes, please reply to this email.
> Am 16.02.2022 um 21:05 schrieb Me <jas_beard(a)hotmail.com>:
> Hello my name is Jason Beard, aka cooltshirtguy. I'm a husband, father,
> and geek. I've been in IT one way or another for over 25 years. I’ve
> and currently learning Ansible. I don't mind learning new things and
> adpat to change.
> Look forward to this new advenmture.
As already said in our IRC meeting: A cordial welcome to our "Adventure Group". :-)
In terms of "don't mind learning new things (and most certainly also trying out/applying) and adpat to change“ server WG opens a wide field. This is especially true of your interest in Ansible. This is one of our (future) work focuses.
Specifically, it's about providing convenient administrative support for services that, according to our program, belong to the main focus of Fedora Server. A good example is PostgreSQL. It is not only about the installation of the RPM, but also, for example, about the incorporation into the Fedora Server Storage concept.
By the way:
All members of our WG use the Fedora people site to provide information and ways of contact. See the member list in the right side box at https://fedoraproject.org/wiki/Server.
Practically, it is about filling the page https://fedoraproject.org/wiki/User:Cooltshirtguy with some content. It’s quite easy (a click on „View source“ opens an opportunity to copy&paste) and among our members there should be a suitable example.
A bit late but hopefully not too late, again, a brief summary of our last IRC meeting right here.
For greater details see meetbot
Full log: https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-...
We are very happy to welcome two new activists to our Server WG:
xtify21 and cooltshirtguy
cooltshirtguy introduced himself on our mailing list:
xtify21 provides information during out IRC meeting:
"work as a sysadmin by day, hack around and getting more into security stuff, help out the almalinux project as well doing some system maintenance stuff for and trying to get more into packing as well with alma and fedora. knowledable of python, shell scripting, and some php"
Both already did "roll up their sleeves and get to work“ (I hope I got the correct translation of a German phrase) and took over parts of testing of the Cockpit file sharing update. And given their range of experience, I look forward to interesting and helpful contributions.
=== Follow up actions ===
info Action: All outstanding articles are published except for two where reviews are available.
=== Cockpit file-sharing update Change Proposal ===
#action: jwhimpel will test Cockpit Module with NFS.
#action: cooltshirtguy and xtify21 will test Cockpit Module with Windows.
=== Specifying F36 manual test requirements ===
#agreed Processing of bug 2054625 is postponed to release F37.
We will continue to determine change details that require manual testing at
So far we will specifically test
#action: jwhimpel will work on Ansible 5 installation and basic testing
=== Preview ===
Next meeting: March 2nd, 17:00 UTC
As it currently appears, we should likely include:
(a) Continuation discussion about F36 Server Edition test requirements and quality assurance.
(b) Continuation Update Fedora Server Technical Specification
In case I miss a topic or you want to discuss another / additional topic, please share it here.
You may have a look at https://pagure.io/fedora-server/boards/Works%20in%20progress to achieve an overview about our current working program.
I have added some info about installation and usage to the pagure ticket so it is easier to track the status:
Please, add your findings using comments or add to the ticket description.
I think this: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2030814
is basically ready to go — it just needs someone with more time than Stephen
or I to take it on and get the package through review and built.
I actually think it'd be a really nice feature to tout for Fedora Server
Edition 36 — maybe something someone would like to make a self-contained
change before that deadline?
Fedora Project Leader
Hello my name is Jason Beard, aka cooltshirtguy. I'm a husband, father,
and geek. I've been in IT one way or another for over 25 years. I've
been using Linux off and on for years but I was a Linux administrator
for the last 10. I've been using Fedora for about 3 years now. My
hobbies include smoking BBQ, gardening, video games, and DIY projects
around the house. Since my youngest started college I have some free
time and want to give back.
I'm not a programmer but I've done some bash scripting. puppet, chef
and currently learning Ansible. I don't mind learning new things and
adpat to change.
Look forward to this new advenmture.