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

DEVPROD-14723 Mark host as needs new agent monitor on unquarantine #8689

Merged
merged 3 commits into from
Feb 7, 2025

Conversation

hadjri
Copy link
Contributor

@hadjri hadjri commented Feb 5, 2025

DEVPROD-14723

Description

It's possible for there to be a race between the agent monitor deploy job and the host monitoring job.

When unquarantining a host back to running, if the monitoring job runs before the agent monitor deploy job, the host will immediately get marked as quarantined again if there is a long interval in its LastCommunicatedTime. During unquarantining, this line causes the host to skip immediate reprovisioning and instead wait for the agent monitor deploy cron job to pick it up later, which opens up the possibility of a potential race.

Changed the unquarantining logic to immediately set NeedsNewAgentMonitorKey: true by copying the same query used by the agent monitor deploy job.

Testing

Unit test changes (this block) fails without the change.

@hadjri hadjri requested a review from a team February 5, 2025 20:56
api/host.go Outdated Show resolved Hide resolved
@hadjri hadjri requested a review from Kimchelly February 6, 2025 23:45
@hadjri hadjri merged commit 4cf80c9 into evergreen-ci:main Feb 7, 2025
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