You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Retry telemetry registration quickly instead of hourly
TelemetryService only retried every iter_min_period (up to 1 hour), but
exordos-bootstrap sets the VS variables it depends on with no systemd
ordering guarantee relative to ec-gservice, so the very first attempt can
silently skip (variables not set yet). With a 1-hour retry period, a
managed realm's ecosystem-side provisioning_timeout (also defaulting to
1 hour) can fire before the next attempt, permanently erroring the realm.
Retry starting at 30s until registration is confirmed, then relax to the
caller's steady-state period immediately. Stands with no network access at
all would otherwise retry every 30s forever, so each failed attempt
doubles the retry period, capped at the steady-state period, until
registration succeeds. Also bump the "variables not configured" log from
DEBUG to INFO so this condition is visible in normal logs.
Signed-off-by: George Melikov <mail@gmelikov.ru>
0 commit comments