entry-port flip: LuCI's :8090/:8443 pair does not converge after a fresh-image install (board mode) — caught by the new installer-contract lane

Aperta
  • Qualcosa non va?
#890 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go
Ambito
backend, devops

Direzione di ricerca

Start with the installer-contract lane in tests/installer-contract/ and trace the fresh-image install path for entry_ui=board. Compare when the entry-ui applier and staged 999-tollgate-admin-setup run against the first-boot UCI defaults, using the uhttpd and UCI dumps described in the issue. Done means a pristine install followed by one reboot serves the LuCI listeners on :8090 and :8443, with the lane passing.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Title: entry-port flip: LuCI's :8090/:8443 pair does not converge after a fresh-image install (board mode) — caught by the new installer-contract lane

Body:

The installer-contract lane (vlab, OpenWrt 25.12.5 x86-64, pristine boot via qemu snapshot
restart, tollgate-wrt-0.6.0_rc1-r0.apk @ 362e5d5) caught a variance in the entry-port
flip (#746 family, the module/portal two-halves contract):

  • Fresh-image install path: after install AND after a reboot, nothing listens on
    :8090/:8443. LuCI is installed (15 luci packages); uhttpd reports running (3/4); the
    uhttpd config carries portal (:2051), trusted (:80) and admin (:8080/:443) — the
    main (LuCI) section has no listen entries at all, so in entry_ui=board mode (the
    mapping file says board, the board's own pair :8080/:443 works, TLS answers) the LuCI
    half of the mapping is simply not served.
  • Contrast (same package, same image, hours earlier on the same VM before the pristine
    restart): :8090/:8443 were listening after install and survived the reboot.

So the LuCI-half convergence is path-dependent: it converged on a device that had booted at
least once before install, and does not converge on a true fresh-image install + one reboot.
Per the README contract, board mode means "LuCI moves to 8090/8443" — an operator following
that doc on a fresh install gets no LuCI until something else re-triggers the applier.

Suspects: the writer that relocates uhttpd.main's listeners (the module's entry-ui
applier vs the staged 999-tollgate-admin-setup half) either runs before LuCI's own
defaults exist on first boot, or its uci state is dropped by the same first-boot
uci-defaults pass that consumes it.

Evidence: lane output ~/ic-out4 on ai-legion (ICFAILED listeners:8090 listeners:8443
alongside the #888 known-red), uhttpd/uci dumps in the session ledger; the lane itself
lands as tests/installer-contract/ and keeps these two listeners asserted, so this stays
red until fixed.

Lingua principale
Go
Stelle
12
Fork
14
Merge medio
3g 20h
PR unite (30g)
261

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenTollGate/tollgate-module-basic-go

Tutte le issue di OpenTollGate/tollgate-module-basic-go

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.