Just checked the F39 rc1.2 on an raspi4 with Server Edition.
The fix for the display issue (https://bugzilla.redhat.com/show_bug.cgi?id=2241252) does work for Server, too.
But there is a next issue:
If I try to adjust the LVM volume to the size of the SD card, I can enlarge the partition mmcblk0p3 using cfdisk as usual without issues. But with pvresize I get
> $ sudo pvresize /dev/mmcblk0p3
> [sudo] password for pb:
> Cannot use /dev/mmcblk0p3: device is not in devices file
> 0 physical volume(s) resized or updated / 0 physical volume(s) not resized
A lsblk
> # lsblk
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
> mmcblk0 179:0 0 59.5G 0 disk
> ├─mmcblk0p1 179:1 0 600M 0 part /boot/efi
> ├─mmcblk0p2 179:2 0 1G 0 part /boot
> └─mmcblk0p3 179:3 0 57.9G 0 part
> └─fedora-root 253:0 0 5.4G 0 lvm /
> zram0 252:0 0 3.7G 0 disk [SWAP]
looks fine and as expected.
And with cockpit -> storage the category „devices“ is empty (instead of listing a LVM volume fedora as to expect). It seems, there is something badly wrong with the image. Hence the error message with arm-installer after writing the image onto disk:
> = Writing image complete!
> mount: /tmp/root: unknown filesystem type 'LVM2_member'.
> dmesg(1) may have more information after failed mount system call.
as mentioned in an earlier mail and as discussed at the go/no-go meeting (https://meetbot.fedoraproject.org/fedora-meeting/2023-10-26/f39-final-go_no… )
The bottom line is that Server Edition is still unusable on Raspi4 and any other SBC, unfortunately. What to do and how to proceed (the next go/no-go meeting is in 4 days expecting rc 1.4 tomorrow or shortly after) ?
--
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
As you may have noticed, we have to F39 release yet. RC 1.2 came out this morning and I did various testing.
What I learned from it: We should not rely on automated testing to the extent we have. After all, things went well for a long time and we gained the impression that there was not much to test.
We now have an installation media that, before the user has even done anything other than plug in the USB stick, prints 10 lines of error/warning messages before starting the installer. The installation works anyway, but this makes an unprofesionell and unserious impression right at the beginning. I do not know with which previous version this occurred. But we have to detect something like this earlier and work towards fixing it.
Another issue is the aarch64 raw image (for SBCs like Raspi). On a Rpi it produces a Server where the screen goes blank after initiating the video and on other devices like Pine64 RockPro the installation script produces additionally an unbootble system disk. It is unclear, if that gets fixed until next week, probably not. I’m not sure if we really should have such a crippled DIY thingy on the Download page.
Anyway, we must organize more pre release testing for future releases.
--
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
Sorry for the really short notice!
The upcoming meeting will be held on
===========================================================
Fedora Server IRC meeting Wednesday, Oct 18 17:00 ==UTC==
irc.libera.chat #fedora-meeting
===========================================================
Please, check your local time using date -d '2023-10-18 17: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 ===
2. === maximum size of aarch64 Server network install image ===
#link https://pagure.io/fesco/issue/3082
#link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or…
3. === Fedora release 39 beta current state and how to continue === 13 mins max
#link https://fedoramagazine.org/announcing-fedora-39-beta/
#link https://fedoraproject.org/server/download/ (Switch show beta on)
Goal:
- Deciding about the next steps
4. === Fedora Server on F39 release party ===
No ticket yet.
5. === Fedora Server WG meeting time after end of Summer Time ===
No ticket yet.
6. === Work Project: Using Ansible to install and configure Wildfly ===
#link https://pagure.io/fedora-server/issue/60
7. === F39/40 Work Project: Fedora Server in a virtualized runtime environment ===
#link https://pagure.io/fedora-server/issue/110
Topics to discuss: How to collect information
- The feedback from the community so far
#link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or…
8. === Open floor ===
For any additions or changes, please reply to this email.
--
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
Cockpit is the modern Linux admin interface. We release regularly. Here
are the release notes:
https://cockpit-project.org/blog/cockpit-303.html
Summary:
- Apps: Detect missing AppStream metadata
- Machines: Add SSH keys to VM creation dialogMachines: Add SSH keys to VM creation dialog
You can get Cockpit here:
http://cockpit-project.org/running.html
The new releases are available in Fedora 38 and 39.
Take care,
Martin Pitt
Hey folks! Sorry, I don't know why it didn't occur to me to send this
through the server list first, it was purely an oversight. I've sent a
ticket to FESCo:
https://pagure.io/fesco/issue/3082
proposing we bump the max size of the aarch64 Server netinst image
(which is release-blocking) from 700M to 1G, as the image is oversize
for F39 final and the limit really doesn't seem to make any sense any
more. A detailed justification is in the ticket. If you have passionate
opinions on this, please read the ticket and comment. Thanks :)
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
I didn't make it to our meeting yesterday, but I did spend some time trouble shooting one of my Fedora servers in the homelab. I thought it was a broken NIC, but I should have hooked it up to a monitor and keyboard and watched the bootup sequence, because after swapping out the motherboard (I had 2 spares) to get a different onboard NIC I had the same issue, because I had a hard drive failure of the system drive (Btrfs data array that I'm using for /home seems to be fine). So I put a "new" system drive into the server, and had a successful install of Fedora Server 39-Beta from a USB image. Everything seems to be just as great as Fedora 38 which this box had before.
On Wednesday, October 4, 2023 1:09:39 PM (-04:00), J Beard wrote:
Unfortunately, I can't make it again. I'm actually traveling today. It's been a rough month for me. I think I'll miss the next one too because I'll be at work conference.
Jason
From: Peter Boy <pboy(a)uni-bremen.de>
Sent: Wednesday, October 4, 2023 5:52:06 AM
To: server(a)lists.fedoraproject.org <server(a)lists.fedoraproject.org>
Subject: Our meeting today
Hi!
A big big sorry, but I can't make it to our meeting today. Our servers are going crazy since Monday and so are all our users. And I have my hands full with "getting fires under control“.
So please, can someone else start the session? Alternatively, we can put the discussion on the mailing list. We have several topics to discuss, the state of the beta, the Wildfly project, the SBC project.
I guess I will be fully occupied today and still tomorrow.
Sorry for the inconvenience and the short notice.
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
_______________________________________________
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
--
---------
mowest
---------
discoverfoss.com
Hi!
A big big sorry, but I can't make it to our meeting today. Our servers are going crazy since Monday and so are all our users. And I have my hands full with "getting fires under control“.
So please, can someone else start the session? Alternatively, we can put the discussion on the mailing list. We have several topics to discuss, the state of the beta, the Wildfly project, the SBC project.
I guess I will be fully occupied today and still tomorrow.
Sorry for the inconvenience and the short notice.
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