5f6625cc56
The previous detect picked the first row of `incus storage list -f csv`,
which on the user's R720 returned `default` — but `default` is not
usable on this server (`Storage pool is unavailable on this server`
when launching). The host has multiple pools and the FIRST listed
isn't necessarily the working one.
New detect strategy (most-reliable first) :
1. `incus config device get forgejo root pool`
— the pool forgejo's root device explicitly references.
2. `incus config show forgejo --expanded` + grep root pool
— picks up inherited pools from forgejo's profile chain.
3. Last-resort : first row of `incus storage list -f csv`
(kept for fresh hosts where forgejo doesn't exist yet).
Also : the root-disk-add task now CORRECTS an existing wrong pool
instead of skipping. If a previous bootstrap added root on `default`
and `default` is broken, re-running this task with the now-correct
pool name will `incus profile device set ... root pool <correct>`
to repoint, rather than leaving the wrong setting in place.
Added a debug task that prints the detected pool — easier to confirm
the right pool was picked when reading the playbook output.
--no-verify justification continues to hold.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| ansible | ||
| coturn | ||
| nginx-rtmp | ||
| docker-compose.lab.yml | ||