kevinveenbirkenbachandClaude Opus 4.8 5b1992005c fix(svc-storage-nfs-server): give the kernel NFS exports distinct fsids ...

Real GitHub Actions and production use the kernel NFS flavor (RUNTIME not in dev/act); only local act uses ganesha. The kernel exports.j2 set no fsid, so the export base and its nested state subdir (one device, a bind-mount under test) get colliding auto-derived NFSv4 fsids; the controller's mount of /srv/nfs/infinito-state then fails with the server returning 'No such file or directory'. Add fsid=1 (base) and fsid=2 (state subdir), mirroring the ganesha flavor's Export_Id 1/2.

Extend the swarm test 12_collect_diagnostics.sh to dump the nfs-server /etc/exports, exportfs -v, ganesha.conf, export tree, nfsd status, and the controller's NFS reachability, so an export failure is diagnosable from the job log instead of only the client-side ENOENT.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-27 23:11:39 +02:00

..

act

…

ci

Merge branch 'main' into feature/swarm-nfs

2026-06-27 17:13:55 +02:00

local

refactor: single /var/lib SPOT + swarm Playwright artifact upload

2026-06-26 17:01:09 +02:00

swarm

fix(svc-storage-nfs-server): give the kernel NFS exports distinct fsids

2026-06-27 23:11:39 +02:00

roundtrip.sh

fix(test-deploy-swarm): actually run the swarm deploy job under act

2026-06-27 21:41:57 +02:00