kevinveenbirkenbachandClaude Opus 5 9a5965b87c fix(web-app-moodle): gate the ownership walks on a settled bootstrap ...

01_manager_ops.yml waits for the moodle container to report healthy and then runs through to the ownership walks, but compose.yml.j2 gives a healthcheck to moodle alone. cron runs the same entrypoint against the same shared code volume and is not covered by that wait, so a bootstrap could still be filling and tearing down .bootstrap.stage while the walks traversed it. That is the 5089 'cannot access' lines and the closing 'Stale file handle' of job 116229890655.

5c3749c437 and 7bc5822421 serialized bootstraps against each other, append-only lock and a sentinel recheck when flock returns EIO across NFS clients. Neither serializes the deploy against a bootstrap, and no condition expressed 'the tree is final' for the deploy to wait on. The walks now wait for the state a finished bootstrap leaves behind: the stage gone and the sentinel holding the expected release. That observes the outcome rather than the lock, so it holds whether or not flock serializes on the mount.

The sentinel path moves to vars/main.yml and reaches the image as an ARG and ENV, like the stage, so the deploy and the entrypoint read one definition instead of two.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-10-15 11:49:15 +02:00

..

files

fix(web-app-moodle): gate the ownership walks on a settled bootstrap

2026-10-15 11:49:15 +02:00

__init__.py

…