Skip to content

artifacts: mtcollins1 boot run 37102391062 evidence (executed MegaRAC media/KVM/SOL/boot after the 0.45.3 reflash) - #13273

Merged
briansrls merged 1 commit into
mainfrom
session/eager-gull-22-mtcollins1-boot-run-37102391062
Oct 4, 2026
Merged

briansrls merged 1 commit into
mainfrom
session/eager-gull-22-mtcollins1-boot-run-37102391062

Conversation

@gunbai-bot

@gunbai-bot gunbai-bot Bot commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

This PR commits the executed evidence from fleet-converge run 37102391062 (mode mtcollins1_boot, 2026-10-03), about 21h after mtcollins1's BMC was reflashed to 0.45.3. The source is GitHub artifact mtcollins1-boot-receipts (id 11269641952). It's committed under artifacts/bmc/mtcollins1-boot-run-37102391062/, and SHA256SUMS lists every file.

Per operation:

  • The boot: mtcollins1-boot-receipt.txt, exit=ok, the attempt id and the timestamps; plus mtcollins1-boot-sol.capture, a one-socket boot to Linux, the workload exit 0, then power down.
  • Media attach: mtcollins1-boot-diagnostics.txt line 1805: medium gunbc-mtcollins1-census-ubuntu-24.04.3-arm64-161b98b9bb389a80.iso, sha256 161b98b9…. Lines 1806–1807 cover the CD handoff (share bound, row started, cd_error_code 0, general-settings readbacks), and line 1815 is the phase timing.
  • KVM still: kvm/journal, kvm/observer.log, kvm/features.json and kvm/still-1..5.jpg. Their sha256s match the ones the receipt binds.
  • Sensor/SDR: the diagnostics bundle carries the BMC sensor/SDR read. It was taken with the host powered off, so the per-CPU sensors read "No Reading". That's evidence the read executed, not evidence of populated sensor values.

Limit. A run receipt names its run, not the controller build. Grounding these operations at 0.45.3 also needs the read-only post-reflash probe (mc info / hpm check). It is pending until the BMC is reachable, and it runs automatically when the BMC comes back. The standing must state that join: executed on 2026-10-03, with the build observed by the probe on its own date, and no firmware-set transition recorded between the two.

The files were scanned for credentials and none are present.

Consumer: untangle cut 3's current-build gate (quick-carp-842). It's a declared frontier under DESIGN §3c.

🤖 Generated with Claude Code

…egaRAC ops after the 0.45.3 reflash)

From the GitHub artifact mtcollins1-boot-receipts (id 11269641952) of
fleet-converge run 37102391062, mode mtcollins1_boot, 2026-10-03, about 21h
after the BMC reflash to 0.45.3: the receipt (exit=ok), the diagnostics bundle
(media attach of the census ISO with its sha256 readback, CD handoff,
share-bound readbacks, and the BMC sensor/SDR read taken with the host powered
off), the SOL capture (a 1P boot to Linux), and the KVM observer journal, log,
features and five stills. Their sha256s match the ones the receipt binds
(still-1 649e3a03...). SHA256SUMS lists every file. The run names itself, not
the controller build: the build must come from the read-only post-reflash
probe (mc info / hpm check). Consumer: untangle cut 3's current-build gate
(quick-carp-842).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@briansrls
briansrls added this pull request to the merge queue Oct 4, 2026
Merged via the queue into main with commit 9cb6f63 Oct 4, 2026
4 checks passed
@briansrls
briansrls deleted the session/eager-gull-22-mtcollins1-boot-run-37102391062 branch October 4, 2026 21:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant