#1697 [kernel] updating F41 Beta in offline mode reboots into maintenance mode due to "ext4 bad orphan inode" errors | rhbz#2318710
Closed by blockerbot. Opened by blockerbot.

Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2318710 **
Information from BlockerBugs App:
2318710

Current vote summary

Commented but haven't voted yet: adamwill

The votes have been last counted at 2024-10-19 18:56 UTC and the last processed comment was #comment-939333

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review
A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)


FInalFE +1
FinalBlocker +1

FinalFE +1

for sure, but for blocker... do we use ext4 as root fs on any of our blocking deliverables?

I believe there might be lots of installations from pre-btrfs times carried over which may be affected by this. Also ext4 is so much important to a Linux system that we should not pass on this one, therefore:

FinalBlocker +1

FinalBlocker +1

We may not ship ext4 as a default, but plenty of people still elect to use it (either due to upgrades from ancient systems or simple preference).

The upgrade criterion is:

"For each one of the release-blocking package sets, it must be possible to successfully complete a direct upgrade from a fully updated, clean default installation of each of the last two stable Fedora releases with that package set installed."

which arguably does exclude this, because no "clean default installation" from the last two releases used an ext4 root partition...

though, if the bug happens on regular system updates, we could equally argue it's covered by the criteria requiring "The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration", and "The installed system must be able appropriately to install, remove, and update software with the default tool for the relevant software type in all release-blocking desktops (e.g. default graphical package manager)". Hmm.

I'll go with the second criterion pointed by Adamwill

FInalFE +1
FinalBlocker +1

OK, I guess that's enough votes to call this.

AGREED AcceptedFinalBlocker

The following votes have been closed:

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

Release F41 is no longer tracked by BlockerBugs, closing this ticket.

Log in to comment on this ticket.

Metadata