[clubanderson]

Fixes #12055

cc @kellyaa — this was observed on your spoke when @clubanderson launched an upgrade from the hub.

Problem

When an upgrade is launched from the hub, the spoke's Version panel shows Status: upgrade retrying / History: Last upgrade: in progress, but the bee-hive "Upgrading…" animation (sidebar Version block, navbar indicator, version chip) is not shown. The animation only appeared when the upgrade was triggered from inside the spoke via the Version panel button.

Root cause

The bee surfaces render only when ctx.upgradeProgress is non-null, and that record lives in localStorage (hive.version.upgradeProgress). It was only ever written by the local click path (selfUpgrade() → versionRecordUpgradeStart()); fetchGitVersion() only read/validated it via versionReconcileUpgradeProgress(). A hub-initiated upgrade reaches the browser solely as v.upgradeMarker (the spoke's on-PVC marker written by the heartbeat handler in src/cmd/hive/main.go) → autoUpdate.state = "retrying", which the frontend used only for status text.

Fix (src/pkg/dashboard/static/index.html)

• New versionAdoptHubUpgradeProgress(v): when there is no local record and /api/version carries a live, non-failed upgradeMarker whose target differs from the running commit, write it into the progress record with source: 'hub' and startedAt from requestedAt. Called from fetchGitVersion() right after versionReconcileUpgradeProgress(), so all existing bee/navbar/chip rendering is reused unchanged.
• The adopted attempt key (target|requestedAt|attempts) is remembered in hive.version.upgradeHubAttempt so a dismissed/expired record is not re-shown for the same attempt; a retry (new attempt) is adopted again.
• versionReconcileUpgradeProgress(): a source: 'hub' record is cleared when the marker disappears without the target landing (abandoned attempt); the marker target also counts as a known target. Landing → existing "Upgraded to …" complete state → cleared after the usual grace.
• source is persisted through versionWriteUpgradeProgress / versionMarkUpgradeComplete.
• Local-trigger behaviour is untouched (a local record is never replaced).

Tests

• New TestSidebarVersionAdoptsHubInitiatedUpgradeProgress (node): adoption, persistence across polls, landing → complete → clear, no re-show for the same attempt, re-adoption on retry, clear when the marker vanishes, failed/landed markers never adopted, local record left alone.
• TestVersionProvenanceRendering extended: the shipped fetchGitVersion() with a hub marker renders the navbar bee + menu progress and hides the Upgrade button; a failed marker does not start the animation; dismissal + no re-show.
• cd src && go build ./... && go test ./pkg/dashboard/... — all green (style/tooltip/parity/import ratchets included).

Forward-port

origin/v6 has the same code (only a typeof guard differs in fetchGitVersion); a v6 PR with the same fix is opened from fix/hub-upgrade-animation-v6.

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign nicholasjackson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

Open PR overlap check

Base branch: v5

Conflicts are checked with every PR merged onto the current tip of v5, so a PR that only needs a rebase is not reported as conflicting with its siblings.

PR	Title	Relation	Files
#12051	🐛 fix(automerge): gate contributor-lane unattended merge on vetted identity	same files	src/pkg/dashboard/static/index.html

[clubanderson]

CI note: server-tests (Dashboard Lint) fails here on dashboard/test/throughput-sla.test.js → prtSLATile renders the p50, n, target and a coloured sparkline. This is pre-existing on v5 since b592ab0 (#12053) — the same job fails on every v5 push since then (b592ab0, 32fc757, c3035b2, 41a6915). Unrelated to this change; Go ./pkg/dashboard/... is green locally and the v6 twin #12074 passes server-tests. Will rebase once v5 is green.

[hivecommons-hive]

Confirmed the server-tests failure is the v5 baseline (same test red on v5 HEAD 299f633). Root cause: #12053 prepended two spans to PRT_SLA_SPANS, shifting the positional lookups in throughput-sla.test.js. Fix opened as #12084; once it lands, re-running checks here should go green without changes to this PR.

---

🐝 Hive Agent: scanner | Instance: hosted-available-oke-11-placeholder-r05x | SHA: 727f16848

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

merged by Hive trusted-author auto-merge: author @clubanderson holds role owner and GitHub permission admin on repo; CI green at b490738.

[github-actions]

Thank you for your contribution! Your PR has been merged.

We'd love to hear how your experience was: share feedback