salvage: uncommitted work from dewey-r180 (disk cleanup #824, 2026-11-06)
This commit is contained in:
1 parent
7f519242e1
commit
80558dfacd
5 files changed
+161
-10
No files matched your search
+14
-3
@@ -387,6 +387,12 @@ one final line with `result` `ok`, `refused`, `gate-failed`,
|
||||
failure that rolled back exits 1, a failed rollback exits 2, usage exits 4. Only one run at a time holds
|
||||
`state/stack-release.lock` (`run-locked`).
|
||||
|
||||
An activation id is the UTC second and the target copy's first 12 characters,
|
||||
`20261020T013708Z-89af38a83afa`. A second run in the same second adds `-1`,
|
||||
then `-2` up to `-9`, the first one with no rollback set, backup or
|
||||
post-attempt store yet, so ids still sort by time. With all ten taken the run
|
||||
refuses `capture-failed` before it stops anything. Adopt uses the same rule.
|
||||
|
||||
1. Once per host, `adopt BUSINESS` records the running stack as the pointer:
|
||||
the copy `stack-copy.sh check` reports, the bus unit's `--pm` and
|
||||
`MOSAIC_CLAUDE_BIN`, the Console's flags without `--checkout`, and the
|
||||
@@ -421,11 +427,13 @@ failure that rolled back exits 1, a failed rollback exits 2, usage exits 4. Only
|
||||
this start. A pass writes the pointer.
|
||||
6. A gate failure puts back the saved units and wrapper, restores the backup
|
||||
when a migration ran, keeps the store it replaced as
|
||||
`bus.post-attempt-<stamp>`, starts the old copy and gates it. If that gate
|
||||
`bus.post-attempt-<stamp>`, where the stamp is the activation's second and
|
||||
its suffix if it has one, starts the old copy and gates it. If that gate
|
||||
fails too, both units stay stopped, the log says `rollback-failed`, and
|
||||
Jason or Mos settles it from the rollback set the message names.
|
||||
7. `rollback BUSINESS` returns to the copy before the pointer's, taken from
|
||||
the log. When the schemas differ it needs `--restore ACTIVATION`; events
|
||||
the log. When the schemas differ it needs `--restore ACTIVATION`, with or
|
||||
without a `-1` to `-9` suffix; events
|
||||
written after that backup need `--events N` with the count it prints, and
|
||||
Jason decides first. It refuses `business-unreadable` and
|
||||
`unknown-kind-for-target` like `activate`. For the second, set each kind
|
||||
@@ -834,7 +842,10 @@ unit write for the authorized operator, with no start/restart verb.
|
||||
`stack-release.sh activate ID BUSINESS --tester-port N` replaces or adds this
|
||||
Console flag in both the installed unit and the pointer. It checks the target
|
||||
copy's own Console before stopping anything; an explicit unsupported request
|
||||
refuses `tester-port-target`. Without an explicit flag, activate and rollback
|
||||
refuses `tester-port-target`. A port outside 1024 to 65535, 7332 or the
|
||||
Console's `--port` is a usage error (exit 4). Under `--plan` both are listed
|
||||
with the plan's other refusals instead, the bad port as `tester-port-invalid`,
|
||||
and the plan exits 3. Without an explicit flag, activate and rollback
|
||||
keep it between supporting copies, or drop it when the target predates support.
|
||||
The plan prints the final Console flags and any dropped `--tester-port N`;
|
||||
the steps log records a drop too. `pm-on` keeps the pointer's Console flags.
|
||||
|
||||
Reference in new issue
Block a user