jschoubben
ba14e2b629
Two things changed at once: a fourth image in the scenario, and scenario machines raised from 1 GiB to 2 GiB. The bootstrap then failed every time, and the image was blamed. Removing the image did not fix it. Removing the memory increase did — nine assertions pass again on three images with the machines back at 1 GiB. Three machines at 2 GiB on a host doing other work contend enough that the store container does not come up at all. The ordinary lesson, and it still caught me: two changes together, the failure attributed to the plausible one, and an issue written recording the wrong cause. What found it was reverting to the exact last-known-good state rather than reverting the suspicious change. What remains untested is whether a fourth image alone is fine. Probably. Nothing has measured it, and the honest state of this issue is that what it was opened about was never demonstrated.
04-ISSUES
The front door for "something is wrong" at the level of the mesh's design or governance. Diagnosis happens here, where the whole mesh is in view; the fix lands in the owning code repository.
What belongs here
| Belongs here | Belongs in the knowledge base |
|---|---|
| The design permits a failure to be silent | How to fix one occurrence of it |
| A documented rule is enforced by nothing | A command that works around it |
| A stated invariant is false in practice | A node-specific quirk |
| The owner is unknown and finding it needs the whole mesh in view | Symptom → fix, once the answer is known |
The knowledge base already holds the operational record and is indexed on symptoms. This folder is not a second copy of it. An issue here is a question HQ must answer; an entry there is an incident someone must clear. An issue whose answer is a general lesson belongs in both.
Structure
NNN-short-name/
00-report.md the symptom as observed, with the evidence; status in frontmatter
01-diagnosis.md the investigation trail, dated, including what was ruled out
Frontmatter, on 00-report.md
---
status: open | diagnosing | located | resolved | wontfix
opened: YYYY-MM-DD
located-in: [] # owning repo(s) or module(s), filled by diagnosis
fixed-by: # pull request or commit reference, filled at resolution
amended-design: # design doc path, when the root cause was a design gap
---
Rules
- Anyone may open an issue. No localisation is required to report one.
- The full flow is playbook
00-META/process/03-issues.md. - Closed issues are never deleted — they are the mesh's symptom-to-component memory.
wontfixis legitimate and requires a sentence saying why.