Skip to content

Fixes a bug preventing rep's disk health check from functioning when run from inside bpm (like it always is run)#1174

Merged
ebroberson merged 2 commits into
developfrom
fix/rep-bpm-disk-health-check-paths
Jul 17, 2026
Merged

Fixes a bug preventing rep's disk health check from functioning when run from inside bpm (like it always is run)#1174
ebroberson merged 2 commits into
developfrom
fix/rep-bpm-disk-health-check-paths

Conversation

@geofffranks

Copy link
Copy Markdown
Contributor

Summary

Adds the necessary paths as writable mounts inside rep

Backward Compatibility

Breaking Change? no

BPM containers only see paths explicitly listed as additional_volumes.
When diego.rep.disk_health_check_paths is configured, rep's diskcheck
runner calls statfs on each path at startup; if any path is absent from
the container's mount namespace it gets ENOENT, which the runner treats
as unhealthy and triggers immediate evacuation.

Loop over disk_health_check_paths in bpm.yml.erb and emit each as a
writable additional_volume so BPM mounts the real host path into the
container before rep starts.

ai-assisted=yes
Mounting root as a BPM additional_volume would expose the entire host
filesystem inside the container. Guard against accidental misconfiguration
by skipping any path that is exactly "/".

ai-assisted=yes
@geofffranks
geofffranks requested a review from a team as a code owner July 17, 2026 18:34

@ebroberson ebroberson left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ebroberson
ebroberson merged commit ac0a21b into develop Jul 17, 2026
9 of 10 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.

2 participants