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

Preventing the use of blackhole detection only when not used #434

Merged
merged 1 commit into from
Aug 15, 2024

Conversation

namrathaurs
Copy link
Contributor

Fixes #415.

Note: This is a patch fix for the prevention mechanism (PR #415) that was added to the blackhole detection mechanism in #331.

TLDR;
PR #415 introduced a bug which resulted in the prevention mechanism to be effective only when the blackhole detection feature was not enabled (via the frontend configuration). When blackhole detection was necessary (aka, enabled), the prevention mechanism still continued to determine that blackhole detection was not needed, when in actual it should be needed. Turns out this was caused as a result of using the wrong case of the variable name involved in the determination logic. Specifically, the variable name should have been glidein_blackhole_rate (shell variable name in the context of condor_startup.sh) instead of GLIDEIN_BLACKHOLE_RATE (which is a frontend knob and is read from glidein_config).

@namrathaurs namrathaurs self-assigned this Aug 13, 2024
@namrathaurs namrathaurs changed the title Fixing the prevention mechanism for blackhole detection when feature is not enabled Preventing the use of blackhole detection only when not used Aug 13, 2024
@mambelli mambelli merged commit 001a6da into glideinWMS:master Aug 15, 2024
9 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