Skip to content

fix(test): wait for the remount in Docker crash-recovery tests - #17

Merged
mattmattox merged 1 commit into
mainfrom
claude/fix-docker-remount-wait
Oct 24, 2026
Merged

mattmattox merged 1 commit into
mainfrom
claude/fix-docker-remount-wait

Conversation

@mattmattox

Copy link
Copy Markdown
Contributor

Main's Docker job fails intermittently (runs 40105056198, 40118141586) in "Journal Crash Recovery Multiple Ops", and "Network Partition" then fails as a knock-on.

After docker start, the test slept about 4s, called start_goclusterfs (which doesn't exist), and read file1.txt. Node restarts on CI take 5-10s to become healthy, so the read hit the unmounted mount point. The logs show start_goclusterfs: command not found followed by cat: /mnt/goclusterfs/file1.txt: No such file or directory. Network Partition then wrote through node1 before its mount was up.

This PR makes both tests that used start_goclusterfs (Multiple Ops and Crash During Write) call wait_node_healthy instead. Split out of #15, where it passed Docker on .66 (34 passed, 0 failed).

🤖 Generated with Claude Code

Journal Crash Recovery Multiple Ops slept 4s after docker start, then
called start_goclusterfs, which does not exist, and read file1.txt from
the still-unmounted mount point. Both CI failures (main run 40105056198,
PR run 40116360883) log "start_goclusterfs: command not found" and
"cat: /mnt/goclusterfs/file1.txt: No such file or directory". Network
Partition then wrote through node1 before it was mounted. Container
restarts take 5-10s on CI. The tests now wait for the node to be healthy.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mattmattox
mattmattox merged commit 109137f into main Oct 24, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant