jfraeys/infra
Watch
1
0
Fork
You've already forked infra
 0
Code Issues 21 Pull requests 5 Projects Releases Packages Wiki Activity Actions

fix(ci): provisioner liveness check ignores host keys of recycled VM IPs #79

Merged
jfraeys merged 1 commit from jfraeys/fix/provisioner-recycled-ip-hostkey into main 2026-10-12 22:24:14 -04:00
Conversation 0 Commits 1 Files changed 1 +3 -1
jfraeys commented 2026-10-12 21:50:00 -04:00
Owner
Copy link

Linode reused 139.177.195.226 for a new VM; the provisioner's known_hosts held the old key, so its runner_service_active ssh failed with 'Host key verification failed'. That function treats any failure as 'runner still alive', so every 30s pass skipped provisioning and all queued jobs waited. The VMs are throwaway (ansible already runs with host key checking off), so use StrictHostKeyChecking=no and UserKnownHostsFile=/dev/null. Takes effect after a deploy of the ci_ephemeral_provisioner role.

🤖 Generated with Claude Code

Linode reused 139.177.195.226 for a new VM; the provisioner's known_hosts held the old key, so its runner_service_active ssh failed with 'Host key verification failed'. That function treats any failure as 'runner still alive', so every 30s pass skipped provisioning and all queued jobs waited. The VMs are throwaway (ansible already runs with host key checking off), so use StrictHostKeyChecking=no and UserKnownHostsFile=/dev/null. Takes effect after a deploy of the ci_ephemeral_provisioner role. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
fix(ci): provisioner liveness check ignores host keys of recycled VM IPs
All checks were successful
Lint / lint (pull_request) Successful in 2m20s
Details
Secret scan / scan (pull_request) Successful in 37s
Details
3f1765f8e4
 
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jfraeys/infra!79
No description provided.