unpushed

FEDORA-2026-0b2b8265d2

FEDORA-2026-0b2b8265d2 created by sgallagh 3 months ago for Fedora 44

Automatic update for fedora-release-44-0.12.

Changelog
* Tue Jan 27 2026 Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> - 44-0.12
- presets: actually enable lvm-devices-import stuff
* Tue Jan 27 2026 Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> - 44-0.11
- presets: enable kmsconvt@.service (rhbz#2429626)

This update was automatically created

3 months ago

This update's test gating status has been changed to 'waiting'.

3 months ago

This update's test gating status has been changed to 'failed'.

3 months ago
User Icon adamwill commented & provided feedback 3 months ago
karma

In openQA testing, this seems to break non-graphical boot. Graphical boot is fine and such tests can also later do ctrl-alt-f3 or ctrl-alt-f6 and get a working VT, but non-graphical boot appears to stop updating the display very early in the boot process and never display a login prompt (presumably this is kmsconvt misbehaving?)

User Icon adamwill commented & provided feedback 3 months ago

I'm not sure if things would be better or worse if this update and FEDORA-2026-b5d576a628 were combined? I can try testing them together on staging, I guess.

User Icon kevin commented & provided feedback 3 months ago

Odd, as fbcon should still be used there... it's only after startup that kmscon is supposed to start...

User Icon adamwill commented & provided feedback 3 months ago

The Cloud image displays a few boot messages before it stops updating the display. Systems installed from a network install image don't show anything after the "Booting <bootloader meun name>" message on x86_64, on aarch64 they show a lot of messages but never reach a VT - the difference there may be that plymouth defaults on for x86_64 but off for aarch64, IIRC.

In each case, switching to tty6 does actually give a working login prompt, sorry I may have implied that it didn't in my earlier message.

User Icon adamwill commented & provided feedback 3 months ago
User Icon jfalempe commented & provided feedback 3 months ago

I don't see anything related to kmscon in the logs you provided.

Maybe it also misses the related kmscon update FEDORA-2026-e4ec48c1b6 ?

User Icon adamwill commented & provided feedback 3 months ago

See my earlier comment. If the systemd and fedora-release changes are interdependent they should have been submitted as a multi-package update. This is in the updates policy.

As I said I'll try and find a minute to test these two separate updates together on staging and see if they work better that way, but if so, they need to be rebuilt together on a side tag to produce a combined update that will pass testing.

User Icon adamwill commented & provided feedback 3 months ago

Oh, I see there's actually a third update involved...that one is stable now, but was not when this update was created, by the looks of it. I can re-run the tests and see if they do any better now.

User Icon adamwill commented & provided feedback 3 months ago

Looks like the tests still fail even with the kmscon update available. Will try with both fedora-release and systemd updates.

User Icon adamwill commented & provided feedback 3 months ago

Testing both updates together makes things worse, if anything - the cloud and netinst image build tests now fail because when we do ctrl-alt-f3 near the end of the test, we get a blank screen.

User Icon jfalempe commented & provided feedback 3 months ago

Thanks for testing the combination of the 3 changes. So a blank screen means probably no getty nor kmscon is started.

User Icon adamwill commented & provided feedback 3 months ago

oddly, in around the last 24 hours, I've started intermittently seeing FreeIPA / AD client tests fail because the test switches to tty3 and sees a blank screen with flashing cursor. Not every time, just sometimes, it never happened before. It's possible the kmscon update alone (which wasn't gated, so it's stable now) caused this somehow, I guess? But I haven't been able to dig into it in detail yet, it might be some other cause entirely...

User Icon jfalempe commented & provided feedback 3 months ago

Is there any logs from kmscon? kmscon is now installed by default, but without the preset, it shouldn't be enabled by default, and shouldn't prevent getty from running.

kmscon is the first package I'm maintaining in Fedora, so I don't know how I can investigate this bug. I will rollback kmscon if it turns out to be the culprit.

This update has been unpushed.

This update was unpushed as part of Fedora 44 Mass Branching because it failed gating tests. Please resubmit these changes for F44 and/or F45/Rawhide.

User Icon supakeen commented & provided feedback 2 months ago

Since the systemd changes were reverted and I thought there was some intermingling of these. Should we resubmit fedora-release with the preset changes applied to see if the cloud images still fail?

If only the boot.iso images fail in OpenQA then we know that we only need to fix up the lorax templates and could do so, but if they affect disk images as well then there are other problems to solve first :)


Please log in to add feedback.

Metadata
Type
unspecified
Karma
-1
Signed
Test Gating
Autopush Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
0 days
Thresholds
Minimum Karma
+2
Minimum Testing
14 days
Dates
submitted
3 months ago
in testing
3 months ago
Builds
0
BZ#2429626 systemd presets request - kmsconvt
0
0

Automated Test Results