[9.3] (backport #13127) Disable dnf-automatic.timer in tests#13137
Merged
Conversation
(cherry picked from commit 3578289)
mergify
bot
requested review from
blakerouse and
swiatekm
and removed request for
a team
github-actions
bot
added
Team:Elastic-Agent-Control-Plane
v1v
approved these changes
Mar 12, 2026
swiatekm
approved these changes
Mar 12, 2026
Member
|
Buildkite test this |
Contributor
💛 Build succeeded, but was flaky
Failed CI Steps
Historycc @swiatekm |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
What does this PR do?
Disables the dnf-automatic.timer service in tests. This was originally missed by #12986.
Why is it important?
We don't retry the RPM install command if it fails due to the lock being held, so if a background process happens to hold it, we fail. We've been seeing failures in the RPM tests recently which may be caused by this problem. See for example: https://buildkite.com/elastic/elastic-agent/builds/35736/steps/canvas?jid=019ce1e1-ec9a-4dbf-9741-5587c7a7006a&tab=output
This problem is fixed in the CI VM definitions by https://github.com/elastic/ci-agent-images/pull/2321, but the VM builds are currently experiencing some issues that we don't want to wait for.
This is an automatic backport of pull request #13127 done by [Mergify](https://mergify.com).