Admin → Cairn Peering: "Global settings" tab never opens (hash rewritten back to #admin/peering) — enable/disable unreachable #684

New issue

Closed

opened 2026-09-23 10:10:34 +00:00 by Cordy · 0 comments

Cordy commented

2026-09-23 10:10:34 +00:00

Owner

Found by the #656 QA pass (v0.6.247, both dogfoods).

Matrix row: §6 Peering — "Enable/disable switch | Toggle peering in admin | Send UI hidden, APIs 503, control plane gated". The row is blocked by this finding.

Steps

Administration → Cairn Peering. The Peers tab is active.
Click Global settings, either with a real mouse click or button.admtab[data-tab=…].click().
Nothing changes. Peers keeps .admtab.active and the content is unchanged.
Setting location.hash = '#admin/peering/<data-tab>' directly is rewritten back to #admin/peering within a second.

The tab's handler is setAdminTab(topic, b.dataset.tab), the same one the working tabs use on Sharing, Retention, Audit, OCM and Users & access (all of those change hash to #admin/<topic>/<tab> and switch correctly). Peering seems to be the one topic whose router doesn't accept a sub-tab. There are no console errors. Reproduced on files and files-bao.

Expected: the Global settings tab opens, showing the peering master switch from v0.4.6 / #134, plus anything else global.
Seen: the tab is unreachable, so the only UI for turning peering off is gone.

Screenshot: 684-peering-global-settings-dead.jpg (taken after the click; Peers still active)

Found by the #656 QA pass (v0.6.247, both dogfoods). **Matrix row:** §6 Peering — "Enable/disable switch | Toggle peering in admin | Send UI hidden, APIs 503, control plane gated". The row is blocked by this finding. **Steps** 1. Administration → Cairn Peering. The Peers tab is active. 2. Click **Global settings**, either with a real mouse click or `button.admtab[data-tab=…].click()`. 3. Nothing changes. `Peers` keeps `.admtab.active` and the content is unchanged. 4. Setting `location.hash = '#admin/peering/<data-tab>'` directly is rewritten back to `#admin/peering` within a second. The tab's handler is `setAdminTab(topic, b.dataset.tab)`, the same one the working tabs use on Sharing, Retention, Audit, OCM and Users & access (all of those change hash to `#admin/<topic>/<tab>` and switch correctly). Peering seems to be the one topic whose router doesn't accept a sub-tab. There are no console errors. Reproduced on files and files-bao. **Expected:** the Global settings tab opens, showing the peering master switch from v0.4.6 / #134, plus anything else global. **Seen:** the tab is unreachable, so the only UI for turning peering off is gone. **Screenshot:** `684-peering-global-settings-dead.jpg` (taken after the click; Peers still active)