Repository navigation
Conversation
The v1 gate and the startup lane's PR checks booted the moving dakota:testing tag. When Dakota published a build that bootc cannot install (2026-11-09, sha256:dc3f6aee), every gate run failed on both sides, v1 stayed held for over a day, and the startup checks went red on unrelated PRs, with no single place showing the cause (#1123). Pin the image in image-versions.yml, which the org's inherited Renovate config already parses. Renovate opens a PR when :testing moves; that PR runs the startup checks, so an image that cannot be installed fails there instead of holding v1. The pin starts at sha256:c10a8b18 (2026-11-08), the newest digest the gate installed and booted (run 42479593163). - update-v1-tag.yml: use image-versions.yml unless V1_GATE_IMAGE is set (emergency override); keep a digest it is given instead of resolving the tag again. - startup-qualification.yml: PR runs boot the pin; manual runs boot the image input; image-versions.yml triggers the lane. - vm_validation_plan.py: a pin bump changes no test, so it needs no gate boot (the bump PR's startup checks cover the image). - Skill docs updated. Refs #1123 Assisted-by: Claude Opus 5.5 via Claude Code Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Danathar <Danathar@users.noreply.github.com>
|
@Danathar this PR is back in your court ( Failing checks:
Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path. Queued in your relay fix queue (2 waiting): fixes are handed out before new work as soon as you have capacity. |
feeb4d8
ℹ️ Sentinel notice — informational; author is trusted (owner), merge is not blockedHive flagged this PR (author @Danathar, head
Hive did not add the |
|
Closing: the image was never the cause. The 11-08 digest this pins failed on ubuntu-26.04 in this PR's own startup checks, but it installed on ubuntu-24.04 on 11-08. The cause is the runner OS; fixed in #1131. |
Summary: testsuite's
v1gate and itsstartupPR checks booted the movingdakota:testingtag. When Dakota published a build that can't be installed (2026-11-09,sha256:dc3f6aee…), every gate run failed on both sides andv1has been held since 2026-11-09 09:41Z (#1123). Thestartupchecks also went red on unrelated PRs (#1127), and nothing showed a single cause. This PR pins the image by digest and lets Renovate bump it through a pull request. A Dakota build that can't be installed then fails that one bump PR, andv1and everything else keep working.What changes
image-versions.yml(new):testingpinned tosha256:c10a8b18…(2026-11-08), the newest digest the gate installed and booted (run 42479593163, which movedv1). The org's inherited Renovate config already has a manager for this file (org-inherited-config.json,customManagers), so Renovate opens a digest-bump PR when:testingmoves.update-v1-tag.ymlV1_GATE_IMAGErepo variable still overrides it in an emergency. A digest it's given is kept instead of being resolved again (before,NAME="${GATE_IMAGE%@*}"dropped it).startup-qualification.ymlimageinput.image-versions.ymlis added to thepull_requestpaths, so a pin bump runs the startup lane, which is what proves the new image installs and boots.scripts/vm_validation_plan.py+ unit teste2e.yml(a human-merge release workflow) isn't touched; callers still pass their own image.How it plays out
startupchecks boot the pinned 11-08 image, so they prove the pinned path works.c10a8b18instead of the broken 11-09 build, which should letv1move again.image-versions.yml(to the 11-09 build) is expected to go red in itsstartupchecks. That's the intended signal: the bump stays open, no automerge, and it tracks v1 tag held by the post-merge VM gate #1123 until a Dakota build installs again.The
V1_GATE_IMAGEvariable (dakota:testing) has already been deleted, so the pin takes effect on merge. Before that, the gate's built-in default was the same tag.Checks run locally
main(nothing new).imageandbaseline_image.image-versions.yml: matches (packageName,currentValue=testing,currentDigest).suites_for_path("image-versions.yml") == ().pytest isn't available on the machine I worked from; CI runs it.
Refs #1123
🤖 Generated with Claude Code