Correct the migration status header to match the host

The header claimed "no target has been migrated" and that the installed
binary was the previous generation. Half of that was stale: yggdrasil
runs the declarative binary and idunn status answers.

The other half was right, and a proposed "correction" to say odin and
heimdall are now Idunn-managed would have been false. Verified on the
host: heimdall.service and odin.service are hand-written units under
/etc/systemd/system, both active, and every idunn-heimdall-* and
idunn-odin-* unit is failed.

The "Correction: Odin is migrated first, not last" section reads like a
completion record and is not one -- it changed the ordering, it did not
migrate a target. Said so in the header, because that misreading has now
happened twice.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Meta Vens 2026-09-08 14:56:00 +02:00
commit cd662cd6da

View file

@ -1,9 +1,17 @@
# Migrating a target onto the current Idunn
Status as of 2026-09-05: **no target has been migrated.** The binary installed
on yggdrasil (`/usr/local/bin/idunn`, 2026-09-02) is the previous generation,
driven by `--swarm-profile` and a root shell actuator. The current binary
rejects that invocation outright:
Status as of 2026-09-08: yggdrasil runs the declarative binary, and **no target
is Idunn-managed.** `heimdall.service` and `odin.service` are hand-written units
in `/etc/systemd/system/`, both active; every `idunn-heimdall-*` and
`idunn-odin-*` unit on the host is failed.
Read the "Correction: Odin is migrated first, not last" section below as an
ordering decision, not as a completion record. It changed which target goes
first. It did not migrate one.
The previous generation was driven by `--swarm-profile` and a root shell
actuator. That invocation is rejected by the installed binary, which is the
clearest way to tell which generation a host is running:
```
$ idunn --swarm-profile yggdrasil-local --store ...