Repository navigation
fix(substrate): re-pin the line to v0.0.27-gs.4 — a golden boot whose image the registry refuses fails with the reason - #391
Conversation
ade3f19 to
d3a5afe
Compare
|
CI: |
d3a5afe to
4d51fae
Compare
Published Helm chart
|
| Chart | agent-platform |
| Version | 4.7.9-dev.fix-substrate-re-pin-gs4.2026-09-11.14-29-42.h43ce12a |
| OCI reference | oci://gsoci.azurecr.io/charts/giantswarm/agent-platform:4.7.9-dev.fix-substrate-re-pin-gs4.2026-09-11.14-29-42.h43ce12a |
| Digest | sha256:dc0ad485b254a7a7d4098391acfa785899ca12364ad573c5f7e38726ad905f8d |
| Registry | public — gsoci.azurecr.io |
| Git catalog | giantswarm-test-catalog (index) |
Pull this chart
helm pull oci://gsoci.azurecr.io/charts/giantswarm/agent-platform --version 4.7.9-dev.fix-substrate-re-pin-gs4.2026-09-11.14-29-42.h43ce12aPosted by architect-orb · build 6204 · commit 43ce12a · updated in place on every push
Published Helm chart
|
| Chart | agent-platform-connectivity |
| Version | 4.7.9-dev.fix-substrate-re-pin-gs4.2026-09-11.14-29-42.h43ce12a |
| OCI reference | oci://gsoci.azurecr.io/charts/giantswarm/agent-platform-connectivity:4.7.9-dev.fix-substrate-re-pin-gs4.2026-09-11.14-29-42.h43ce12a |
| Digest | sha256:01f785d75b9a52470889b746ccc0844b9683d8e75850eb76cac9248bc8d75bb1 |
| Registry | public — gsoci.azurecr.io |
| Git catalog | giantswarm-test-catalog (index) |
Pull this chart
helm pull oci://gsoci.azurecr.io/charts/giantswarm/agent-platform-connectivity --version 4.7.9-dev.fix-substrate-re-pin-gs4.2026-09-11.14-29-42.h43ce12aPosted by architect-orb · build 6207 · commit 43ce12a · updated in place on every push
… image the registry refuses fails with the reason The Substrate line's fourth release of upstream 0.0.27 carries giantswarm/substrate#14: the image cache tags a registry's final word (a 4xx other than 408/429) with ReasonFailedGetExternalObject, atelet's Run/Restore boundaries claim it, ate-api crashes the actor with the registry's answer and the ActorTemplate reconciler records the cause on the template. A Harness whose workload.image cannot be pulled fails its golden boot at once as Ready=False ActorTemplateFailed (GoldenActorCrashed: … MANIFEST_UNKNOWN) instead of sitting in ActorTemplatePending with a worker pinned (measured at 300 s without a message on gs.2; giantswarm/giantswarm#37742 row 27). components.substrate/components.substrate-crds move to >=0.0.27-gs.4 <0.0.28-0 and kagent.substrateWorkerPool.workerImage to 0.0.27-gs.4; examples/customer-bom.yaml and tests/verify-components.py move with the pin. Inert behind the fleet's <4.0.0 bound.
4d51fae to
43ce12a
Compare
Re-pins the Substrate line to
v0.0.27-gs.4(giantswarm/giantswarm#37757; giantswarm/giantswarm#37742 row 27; epic giantswarm/giantswarm#37705).Why
A Harness whose
workload.imagecannot be pulled — a digest the registry answers 404 for, a repository the pull may not read — never booted and was never reported ongs.2: ate-api retried the failedResumeActorwith backoff,GoldenSnapshotStatus.ErrorMessagestayed empty, kagent reportedReady=False ActorTemplatePendingfor as long as anyone waited, and a worker stayed pinned to the golden actor (measured in giantswarm/agent's ATS: 300 s, no message — giantswarm/agent#26).v0.0.27-gs.4(tag onbbe92143) =gs.3+ giantswarm/substrate#14: the image cache tags a registry's final word (a 4xx other than 408/429) withReasonFailedGetExternalObject, atelet's Run/Restore boundaries claim it, ate-api crashes the actor with the registry's answer and releases the worker, and the ActorTemplate reconciler records the cause on the template. kagent turns it intoReady=False ActorTemplateFailed—GoldenActorCrashed: actor ate-golden/<uid> crashed: … MANIFEST_UNKNOWN: manifest unknown— in seconds.What moves
components.substrate/components.substrate-crds→>=0.0.27-gs.4 <0.0.28-0;kagent.substrateWorkerPool.workerImage→ghcr.io/giantswarm/substrate/ateom-gvisor:0.0.27-gs.4;examples/customer-bom.yamlandtests/verify-components.py(SUBSTRATE_RANGE,SUBSTRATE_PIN) move with the pin; the README/UPGRADE range mentions and the chart README follow.make verify-componentsgreen locally.Overlaps #390 (the
gs.3re-pin for the CRD keep policy) on the same pin lines:gs.4containsgs.3; whichever merges second rebases.Verification
FORK.mdrelease row carries the digests).execute-chart-tests) installs Substrate from the chart at the range's resolution, i.e.gs.4, and runs the agent path on it.gs.4end to end (test_fail_fast.py::test_unpullable_harness_image_fails_fast, giantswarm/agent PR linked in #37742 row 27).No installation acts — the release stays inert behind the fleet's
<4.0.0bound.