#44 1855034 Creating an armhfp disk image with btrfs results in an empty filesystem
Closed 3 years ago by blockerbot. Opened 3 years ago by blockerbot.

Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1855034

Current vote summary

The votes have been last counted at 2020-08-27 23:18 UTC and the last processed comment was #comment-673885

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review


I don't think it can be a blocker. The affected images are only 32-bit ARM desktop images. The Minimal image is possibly affected by the fix, but isn't affected by the bugs because it doesn't use Btrfs.
https://fedoraproject.org/wiki/Releases/33/ReleaseBlocking

But I think it should be fast tracked for beta FE. (a) reverting Btrfs on desktop arm means reverting it for desktop aarch64, or (b) invasive changes to separate arm and aarch64 kickstarts. (Or something like that.)

BetaFE +1
BetaBlocker -1
(because as chris said, no release-blocking deliverables are impacted)

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

3 years ago

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

Login to comment on this ticket.

Metadata