Skip to content

#67 docs: tailnet flaps — the rule, the 2026-10-22 signature, and how to tell it apart - #69

Merged
gregoryfoster merged 7 commits into
mainfrom
67-flap-rule
Oct 23, 2026
Merged

gregoryfoster merged 7 commits into
mainfrom
67-flap-rule

Conversation

@gregoryfoster

@gregoryfoster gregoryfoster commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Closes #67.

Docs only: no code and no deploy.

  • DEPLOYMENT.md § Tailnet flaps (new):
    • the operator's rule, word for word;
    • the two flaps so far, each with its kind;
    • the 2026-10-22 signature: balloon pressure, then backoffs, a silent journal, time-jumped(33s), at most one failed check-in, and recovery with NRestarts=0;
    • how to tell a flap from a broker-side event (the 10-13 patch run as the control) or from a tailscaled restart (Tailscale 1.104.2 for TS-2026-013 (eMudhra intermediates) #65);
    • triage commands, each run against the real 10-22 window.
  • AGENTS.md: the Detail Docs line names the section.

Cause and the decision are recorded in this comment. Cohort answers from the Mayfly questionnaire land on #67 as they arrive.

Verified: uv run pytest on the doc-reading tests passes (191 passed), and ruff is clean.

🤖 Generated with Claude Code

gregoryfoster and others added 2 commits October 23, 2026 04:42
… to tell it apart

The operator's rule (2026-10-23) replaces "a second flap gets an issue":
a flap gets an issue only if it delays a command, pages, or outlasts
liveness's 900 s grace; others are logged on the epic.

The 2026-10-22 flap was host-side: virtio_balloon "Out of puff" at
04:13:26-38Z, then tailscaled's rebind-reason=[time-jumped(33s),...]:
the VM most likely paused about 33 s. The 2026-10-10 flap was path churn
with neither. exe.dev's docs explain neither.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Mayfly questionnaire answers (synthesis on #67): co-broker and
co-replicator, behind 32.185.164.108 like co-processor, each logged
balloon pressure then a 31-33 s time jump; archiver, provisioner and
watcher, on other egress, only lost the broker. Replaces "silent 68 s"
(true only excluding tailscaled and Processor) with the 32.7 s hole.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gregoryfoster and others added 5 commits October 23, 2026 04:52
…ed per VM

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s later pause

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…n small VMs

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@gregoryfoster
gregoryfoster merged commit a23970b into main Oct 23, 2026
2 checks passed
@gregoryfoster
gregoryfoster deleted the 67-flap-rule branch October 23, 2026 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Second tailnet flap (2026-10-22 04:13–04:15Z): ridden out; decide the flap rule

1 participant