This was originally discovered by @pwhalen when trying to produce them during the first Btrfs test day.
This is a stub for RHBZ#1855034.
The initial work to make appliance-tools actually create Btrfs images at all was done over the following pull requests by @dcavalca:
Additionally, Davide and I discovered that fixes needed to be done to Koji and Mock in order to get the builds to successfully run in the build environment, which we did:
The patches were deployed to the build system infrastructure on August 8 (pagureio#fedora-infrastructure#9194), and after that, the images were successfully being created and published.
Unfortunately, we still have a problem. Per @pwhalen, the firmware files are getting installed into the Btrfs volume rather than the dedicated boot and firmware volumes in the image, which makes it so that the image does not work on ARM devices. For some reason, something is happening in the wrong order still...
This appears to be fixed with the merge of the following PRs:
With appliance-tools-010.2, all the fixes have been made to produce a working test image according to @pwhalen. Final confirmation is pending the nightly compose run that builds all the images.
appliance-tools-010.2
Metadata Update from @ngompa: - Issue assigned to ngompa (was: dcavalca)
Well, the image is now constructed correctly, but apparently we have broken bootloader and fstab(5) configuration, so I've made a PR to appliance-tools to try to fix that: https://pagure.io/appliance-tools/pull-request/17
fstab(5)
appliance-tools
With appliance-tools-011.1, everything should work, per @pwhalen. The Rawhide nightly compose run that builds the images will verify this.
appliance-tools-011.1
The update has been submitted to Bodhi (FEDORA-2020-c6d9203505) and @adamwill has made the request to Fedora Release Engineering to land it for the F33 Beta composes.
Issue status updated to: Closed (was: Open) Issue close_status updated to: Fixed
Verified as fixed with the latest compose.
Login to comment on this ticket.