Skip to content

[ci-maintainer] Post-Testing E2E: gaming flavors fail to install — live kernel has no btrfs module (unknown filesystem type 'btrfs') #136

Closed

Description

@hivecommons-hive

CI Issue

Post-Testing E2E fails for both gaming flavors (utah-gaming,
utah-nvidia-gaming) during phase 3, when the installer formats and mounts
the LUKS-backed root. mkfs.btrfs succeeds, then the mount is refused:

+ mkfs.btrfs -f -L root /dev/mapper/fisherman-root
WARNING: failed to open /dev/btrfs-control, skipping device registration: No such file or directory
btrfs-progs v7.1
+ mount -t btrfs /dev/mapper/fisherman-root /mnt/fisherman-target
mount: /var/mnt/fisherman-target: unknown filesystem type 'btrfs'.
fisherman: fatal: mounting root: ... exit status 32

blkid confirms the filesystem was created (TYPE="btrfs"), so this is the
live environment's kernel lacking a loadable btrfs module — the missing
/dev/btrfs-control is the same symptom — and not a bad filesystem or a
cryptsetup problem. The non-gaming flavors in the same run install fine and
get all the way to a GNOME login, so this is specific to the kernel the
gaming flavors ship.

Evidence

Run https://github.com/projectbluefin/utah/actions/runs/35374557822
(workflow_dispatch on main, commit 2216657):

  • job 105696128282 (utah-nvidia-gaming) — failed 17:46:56Z at the mount
  • job 105696128303 (utah-gaming) — failed 17:42:49Z, same step
  • jobs 105696128208 (utah-nvidia) / 105696128221 (utah) reached phase 6
    and failed later, for an unrelated OCR-gate reason tracked separately

Because promote-to-testing needs the whole luks matrix, no digest is
promoted while these two flavors fail, so this blocks promotion on its own.

Recommendation

Determine why the gaming-flavor live ISO has no btrfs kernel module — the
most likely cause is a flavor kernel swap whose kernel-modules package is
not installed into (or not carried through into) the live environment — then
either install the matching modules package or assert its presence during the
image build so the failure surfaces at build time instead of at install time.

A cheap pre-check in the installer path (modprobe btrfs before mkfs.btrfs,
failing with a clear message) would turn this into a one-line diagnosis for
the next occurrence.

This one is a product/image defect, not a CI configuration defect: filing it
for the image owners rather than fixing it here.


Filed by ci-maintainer agent (ACMM L4/L5 — hold-gated mode)

— hive: agent=ci-maintainer backend=copilot model=claude-opus-5 copilot=1.0.78

Activity

  1. added
    hive/likely-doneHive verified that a merged PR references or claims this issue; pending confirmation
    on Sep 25, 2026
  2. castrojo commented on Sep 26, 2026

    @castrojo
    Contributor

    This was generated by AI during triage.

    Closing as completed: resolved by PR #158 (commit 0cfe1bf), enabling CONFIG_BTRFS_FS as a kernel module for gaming flavors and adding verification in luks-e2e.sh.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent/ci-maintainerFiled or owned by the ci-maintainer agent.hive/likely-doneHive verified that a merged PR references or claims this issue; pending confirmation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions