Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move the probedb.py script #467

Open
ksuderman opened this issue Apr 18, 2024 · 5 comments
Open

Move the probedb.py script #467

ksuderman opened this issue Apr 18, 2024 · 5 comments
Assignees

Comments

@ksuderman
Copy link
Contributor

ksuderman commented Apr 18, 2024

The probedb.py script that is used for the livenessProbe (and others) lives in the /tmp directory, so eventually the tmp cleanup job to be added in #448 will break the probes. Move the script somewhere like /usr/local/bin/ before #448 is merged.

@ksuderman ksuderman added the bug label Apr 18, 2024
@ksuderman ksuderman self-assigned this Apr 18, 2024
@nuwang
Copy link
Member

nuwang commented Apr 18, 2024

The mapped file should be read-only and not deletable I believe, so I don't think the cleanup screen will affect it, but if there's a better location we can move it to, that would still make sense.

@ksuderman
Copy link
Contributor Author

I just checked on a cluster I just launched and the probedb.py script is rw for root and the cron jobs run as root by default. We could set the mode to 444 or 400 or something similar, but that might just lead to unexpected surprises in the future. I'll get a PR for this ASAP since the maintenance PR was merged.

@nuwang
Copy link
Member

nuwang commented Apr 19, 2024

Can root actually delete it though? I think even root should be unable to affect that file.

@ksuderman
Copy link
Contributor Author

Good point. Since it is a config map and not an actual file it shouldn't be deletable. I'll test, but I would feel better if the script didn't live in /tmp

@ksuderman ksuderman added paper-cut and removed bug labels Apr 22, 2024
@ksuderman
Copy link
Contributor Author

This is a bit of a false alarm. The cronjob cleans up /galaxy/server/database/tmp and not the /tmp directory where the probedb script lives. It might be a best practice to move it somewhere like /usr/local/bin, but it is not urgent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants