jschoubben
acd5a0d80b
Against a real ACME server the proxy orders, the challenge is answered at the name on port 80 through the proxy itself, the authorisation goes valid, finalisation is accepted, and the authority issues a certificate. The client then posts to an empty URL to collect it, and never does. Read from the authority's own log rather than inferred. Across one run it issued two certificates and accepted finalise three times: the client reaches issuance every attempt and fails at the same step after it. Ruled out and recorded, so nobody repeats it: the directory is complete; the authority's API certificate covers the address; the challenge path works. A hand-written server config was suspected and was wrong — replacing it with the server's own default, changing only the challenge port, gives the identical error. Filed rather than pursued because what remains is interop between two libraries against a server that exists to be a test server, and may say nothing about a real authority. What the mesh needed to show, it showed: a routed name gets a certificate ordered from a configured authority, and an unrouted one gets nothing — that second assertion passes. Phase 1 closes with this one item partly open. Two of its four tasks needed no code at all, the network shape was built, and the next thing to learn comes from moving a module rather than a fourth lab run.
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.