Cherry-pick #24387 to 7.x: Fix failing installation on windows 7 #24409
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #24387 to 7.x branch. Original message:
What does this PR do?
Issue described here: #24327
there was a race between enrollment process and restarting service, FS playing part as well.
The thing was that when agent was restarted only on windows 7 it loaded standalone ID, even though it was already replaced by enrollment process.
Then when agent retrieved hosts from fleet it even overwrote updated ID with stale one.
This fix adds a lock which prevents simultaneous write in between these two processes and a forced Reload in case of fleet managed agent later in the cycle.
Another thing is FSync after file rotation which was missing for windows.
These seems to fix the issue, tested on win 7 VM on cloud
Why is it important?
Fixes #24327
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.