Skip to content

Re-validate immutable bootc/rpm-ostree status scenarios on a current image #838

Closed

Description

@kylerankin

Blocked re-validation of two @pending immutable-OS scenarios from #833 that need a live QEMU bootc VM to re-run.

These two scenarios in tests/common/features/common_immutable.feature cite blockers that predate recent bootc releases; status population in a fresh QEMU install has likely improved, but nothing can re-check them without a manual boot:

  • No RPM packages are layered on the base image — rpm-ostree status --json reportedly fails in a fresh QEMU bootc install, so the test cannot distinguish "no layers" from "no answer".
  • bootc status shows a pinned image — bootc status reportedly not reliably populated in a fresh QEMU install.

Reproduce / re-validate

Boot a current ghcr.io/projectbluefin/bluefin:testing (or :latest) image in QEMU, SSH in as the test user, and run manually:

rpm-ostree status --json
bootc status --json

If both populate correctly, remove the @pending tag from each scenario and re-run the common suite. If either still fails, re-anchor that scenario's @pending comment to a fresh issue and leave it pending with the specific failure captured.

Originally flagged in #833 (no tracking issue existed for these two blockers).

🐝 Hive Agent: contributor | SHA: db329ee6

Activity

  1. kylerankin commented on Sep 21, 2026

    @kylerankin
    ContributorAuthor

    Re-validation of these two @pending immutable-OS scenarios requires booting a current Bluefin image (e.g. ghcr.io/projectbluefin/bluefin:testing) in QEMU and running rpm-ostree status --json / bootc status --json, then either un-pending the scenarios (if status populates) or re-anchoring the @pending comment to a fresh issue (if it does not). That decision cannot be made from this environment:

    • No boot capability here — no /dev/kvm, no qemu-system-*, no virsh/libvirt, no docker/podman, and no pre-pulled Bluefin image. rpm-ostree status / bootc status read booted-ostree runtime state, so a container pull is not a substitute for a live boot. The full image boot only happens in the separate e2e.yml workflow (triggered by projectbluefin/lab against a target-image); pr-validate.yml only lints, checks quarantine age, and checks the coverage snapshot — it never boots an image.
    • Un-pending without that boot would violate Re-validate immutable bootc/rpm-ostree status scenarios on a current image #838's explicit "re-validate on a current image" requirement (a tag-only PR has no evidence behind it), and it is also not cleanly shippable right now: un-pending changes the common suite counts, which forces regenerating the coverage snapshot in docs/skills/test-authoring/suite-map/SKILL.md, and the runtime-gate pattern this repo uses (@requires_* in before_scenario) needs tests/common/features/environment.py. Both files are owned by open PRs chore: remove bluefinctl test coverage #822 (DIRTY) and test(smoke): skip @vm_only scenarios in container lanes #740 (suite-map/SKILL.md), so a disjoint PR can't be opened until they land.

    Waiting on: a current Bluefin image booted in the lab (projectbluefin/lab build/VM) so the two scenarios can be run and the pass/fail decision made. Once that's available (and #822/#740 have merged, freeing environment.py and the coverage snapshot), the fix is minimal: remove @pending from the two scenarios and regenerate the coverage snapshot.

    — hive: backend=pi model=lemonade/Ornith-1.5-35B-A3B-GGUF-Q6_K

    🐝 Hive Agent: contributor | SHA: db329ee6

  2. added
    blockedWaiting on something outside this repository. Use `/label blocked` or `/remove-label blocked`.
    on Sep 21, 2026
  3. added
    triage/acceptedScope accepted; ready for work. Use `/triage accepted`.
    and removed on Oct 13, 2026
  4. added
    stage/010-actionableTriaged; eligible for the hive to pick up
    stage/stalledIn its current stage longer than expected
    and removed
    stage/010-actionableTriaged; eligible for the hive to pick up
    stage/stalledIn its current stage longer than expected
    blockedWaiting on something outside this repository. Use `/label blocked` or `/remove-label blocked`.
    on Oct 15, 2026
  5. hivecommons-hive commented on Oct 22, 2026

    @hivecommons-hive
    Contributor

    Unblocked: the blocked label was applied by the hive without a blocked-on marker, so nothing could lift it. This issue is actionable again.

  6. 64 remaining items

  7. Karibhou commented on Nov 6, 2026

    @Karibhou
    Contributor

    Summary: The requested changes are prepared so the two image checks can be tried on a freshly started system. They are not yet verified on a running image, and repository rules prevent opening a second pull request that changes the same file as an existing one.

    What I need from you: Resolve the overlapping pull request, then open and run the prepared change before merging it.


    Prepared branch: Karibhou:hive/issue-838-immutable-validation, commit d397ece4. It removes the two pending tags and regenerates the coverage snapshot. Open PR #1076 also modifies docs/skills/test-authoring/suite-map/SKILL.md; repository policy requires waiting for it to land or closing the overlap before opening another PR.

    Local checks: common-suite Behave dry run, Ruff, coverage snapshot check, documentation validation and skill index check passed. The live run is still required: dispatch manual.yml with suites=common, test_ref set to the PR head, and image=dakota:testing pinned by digest, as approved in the issue; do not merge before it passes.

    — hive: backend=omp model=openai-codex/gpt-6.1-terra


    🐝 Hive Agent: contributor | SHA: d397ece4

  8. added
    has-open-prAn open PR already links this issue with Fixes/Closes/Resolves; the hive will not dispatch it again
    and removed
    stage/010-actionableTriaged; eligible for the hive to pick up
    on Nov 6, 2026
  9. hivecommons-hive commented on Nov 9, 2026

    @hivecommons-hive
    Contributor

    PR #1116 covers this issue: #1116

    The PR body says this is partial/non-closing work (Refs/Part of or leave-open wording), so Hive will not add a closing keyword. GitHub will not show its issue-list PR icon without a closing keyword; the stage comment is the link.

  10. added
    stage/010-actionableTriaged; eligible for the hive to pick up
    stage/stalledIn its current stage longer than expected
    and removed on Nov 9, 2026
  11. Danathar commented on Nov 11, 2026

    @Danathar
    Contributor

    Re-validated on a current image: manual run 42923513204 (ghcr.io/projectbluefin/utah:testing, common, with the #1138 mount fix) booted and both scenarios passed: 'No RPM packages are layered on the base image' and 'bootc status shows a pinned image'. common-a 52 passed, common-b 36 passed, no scenario failures. Nothing left to do here.

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

    approved-directionhas-open-prAn open PR already links this issue with Fixes/Closes/Resolves; the hive will not dispatch it againhive/partially-addressedA merged PR addressed only part of this issue; remainder still actionablekind/cleanupTech debt, refactoring, tests or process.triage/acceptedScope accepted; ready for work. Use `/triage accepted`.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions