Skip to content

Make redhat exhaustive test install command more robust #17592

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Apr 29, 2025
Merged

Make redhat exhaustive test install command more robust #17592

merged 1 commit into from
Apr 29, 2025

Conversation

donoghuc
Copy link
Member

@donoghuc donoghuc commented Apr 28, 2025 •
edited
Loading

Release notes

[rn:skip]

What does this PR do?

We are seeing a frequent issue in CI where tests are failing to install via package manager on rhel8. It looks like the issue may be due to processes that are being terminated and leaving behind lock files on the rpm database. This commit udpates the install method to try to do a database rebuild routine which will force lock files to be removed. This fix assumes that at the time of testing, our tests should take priority over any package manager operation and we can prioritize our command over anything else that may be interacting with the package manager.

Why is it important/What is the impact to the user?

N/A

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • [ ] I have made corresponding changes to the documentation
  • [ ] I have made corresponding change to the default configuration files (and/or docker env variables)
  • [ ] I have added tests that prove my fix is effective or that my feature works

Related issues

Logs

2025-04-27 23:07:51 PDT | 1) artifacts composition prohibited gem dependencies does not vendor any version of kramdown
-- | --
  | 2025-04-27 23:07:51 PDT | Failure/Error: logstash.install({:version => LOGSTASH_VERSION})
  | 2025-04-27 23:07:51 PDT |  
  | 2025-04-27 23:07:51 PDT | ServiceTester::InstallException:
  | 2025-04-27 23:07:51 PDT | RPM: error: db5 error(-30969) from dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch
  | 2025-04-27 23:07:51 PDT | RPM: error: cannot open Packages index using db5 -  (-30969)
  | 2025-04-27 23:07:51 PDT | RPM: error: cannot open Packages database in /var/lib/rpm
  | 2025-04-27 23:07:51 PDT | Error: Could not run transaction.
  | 2025-04-27 23:07:51 PDT | # ./rspec/commands/redhat.rb:48:in `install'
  | 2025-04-27 23:07:51 PDT | # ./rspec/commands.rb:135:in `install'
  | 2025-04-27 23:07:51 PDT | # ./acceptance/spec/lib/artifact_composition_spec.rb:24:in `block in <main>'
  | 2025-04-27 23:07:51 PDT | # ./Rakefile:30:in `block in <main>'
  | 2025-04-27 23:07:51 PDT |  
  | 2025-04-27 23:07:51 PDT | Finished in 29 minutes 31 seconds (files took 1.79 seconds to load)
  | 2025-04-27 23:07:51 PDT | 30 examples, 1 failure, 1 pending
  | 2025-04-27 23:07:51 PDT |  
  | 2025-04-27 23:07:51 PDT | Failed examples:
  | 2025-04-27 23:07:51 PDT |  
  | 2025-04-27 23:07:51 PDT | rspec ./acceptance/spec/lib/artifact_composition_spec.rb:33 # artifacts composition prohibited gem dependencies does not vendor any version of kramdown

@donoghuc
Make redhat exhaustive test install command more robust
67260df 
We are seeing a frequent issue in CI where tests are failing to install via
package manager on rhel8. It looks like the issue may be due to processes that
are being terminated and leaving behind lock files on the rpm database. This
commit udpates the install method to try to do a database rebuild routine which
will force lock files to be removed. This fix assumes that at the time of
testing, our tests should take priority over any package manager operation and
we can prioritize our command over anything else that may be interacting with
the package manager.
@mergify
Copy link
Contributor

mergify bot commented Apr 28, 2025

This pull request does not have a backport label. Could you fix it @donoghuc? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
  • If no backport is necessary, please add the backport-skip label

@elastic-sonarqube
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@donoghuc
Copy link
Member Author

Exhaustive tests kicked off: https://buildkite.com/elastic/logstash-exhaustive-tests-pipeline/builds/1788

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

kaisecheng
kaisecheng approved these changes Apr 29, 2025
View reviewed changes
Copy link
Contributor

@kaisecheng kaisecheng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM ❤️

@donoghuc donoghuc added the backport-active-all Automated backport with mergify to all the active branches label Apr 29, 2025
@donoghuc donoghuc merged commit 01962f6 into elastic:main Apr 29, 2025
10 checks passed
@github-actions
Copy link
Contributor

@Mergifyio backport 8.17 8.18 8.19 9.0

@mergify
Copy link
Contributor

mergify bot commented Apr 29, 2025 •
edited
Loading

backport 8.17 8.18 8.19 9.0

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Apr 29, 2025
@donoghuc @mergify
Make redhat exhaustive test install command more robust (#17592)
4bbedc4 
We are seeing a frequent issue in CI where tests are failing to install via
package manager on rhel8. It looks like the issue may be due to processes that
are being terminated and leaving behind lock files on the rpm database. This
commit udpates the install method to try to do a database rebuild routine which
will force lock files to be removed. This fix assumes that at the time of
testing, our tests should take priority over any package manager operation and
we can prioritize our command over anything else that may be interacting with
the package manager.

(cherry picked from commit 01962f6)
mergify bot pushed a commit that referenced this pull request Apr 29, 2025
@donoghuc @mergify
Make redhat exhaustive test install command more robust (#17592)
65e2e9a 
We are seeing a frequent issue in CI where tests are failing to install via
package manager on rhel8. It looks like the issue may be due to processes that
are being terminated and leaving behind lock files on the rpm database. This
commit udpates the install method to try to do a database rebuild routine which
will force lock files to be removed. This fix assumes that at the time of
testing, our tests should take priority over any package manager operation and
we can prioritize our command over anything else that may be interacting with
the package manager.

(cherry picked from commit 01962f6)
mergify bot pushed a commit that referenced this pull request Apr 29, 2025
@donoghuc @mergify
Make redhat exhaustive test install command more robust (#17592)
679d522 
We are seeing a frequent issue in CI where tests are failing to install via
package manager on rhel8. It looks like the issue may be due to processes that
are being terminated and leaving behind lock files on the rpm database. This
commit udpates the install method to try to do a database rebuild routine which
will force lock files to be removed. This fix assumes that at the time of
testing, our tests should take priority over any package manager operation and
we can prioritize our command over anything else that may be interacting with
the package manager.

(cherry picked from commit 01962f6)
mergify bot pushed a commit that referenced this pull request Apr 29, 2025
@donoghuc @mergify
Make redhat exhaustive test install command more robust (#17592)
99db020 
We are seeing a frequent issue in CI where tests are failing to install via
package manager on rhel8. It looks like the issue may be due to processes that
are being terminated and leaving behind lock files on the rpm database. This
commit udpates the install method to try to do a database rebuild routine which
will force lock files to be removed. This fix assumes that at the time of
testing, our tests should take priority over any package manager operation and
we can prioritize our command over anything else that may be interacting with
the package manager.

(cherry picked from commit 01962f6)
donoghuc added a commit that referenced this pull request Apr 29, 2025
@mergify @donoghuc
Make redhat exhaustive test install command more robust (#17592) (#17601
4088e9a 
)

We are seeing a frequent issue in CI where tests are failing to install via
package manager on rhel8. It looks like the issue may be due to processes that
are being terminated and leaving behind lock files on the rpm database. This
commit udpates the install method to try to do a database rebuild routine which
will force lock files to be removed. This fix assumes that at the time of
testing, our tests should take priority over any package manager operation and
we can prioritize our command over anything else that may be interacting with
the package manager.

(cherry picked from commit 01962f6)

Co-authored-by: Cas Donoghue <[email protected]>
donoghuc added a commit that referenced this pull request Apr 29, 2025
@mergify @donoghuc
Make redhat exhaustive test install command more robust (#17592) (#17602
bc46a5e 
)

We are seeing a frequent issue in CI where tests are failing to install via
package manager on rhel8. It looks like the issue may be due to processes that
are being terminated and leaving behind lock files on the rpm database. This
commit udpates the install method to try to do a database rebuild routine which
will force lock files to be removed. This fix assumes that at the time of
testing, our tests should take priority over any package manager operation and
we can prioritize our command over anything else that may be interacting with
the package manager.

(cherry picked from commit 01962f6)

Co-authored-by: Cas Donoghue <[email protected]>
donoghuc added a commit that referenced this pull request Apr 29, 2025
@mergify @donoghuc
Make redhat exhaustive test install command more robust (#17592) (#17603
2153b7d 
)

We are seeing a frequent issue in CI where tests are failing to install via
package manager on rhel8. It looks like the issue may be due to processes that
are being terminated and leaving behind lock files on the rpm database. This
commit udpates the install method to try to do a database rebuild routine which
will force lock files to be removed. This fix assumes that at the time of
testing, our tests should take priority over any package manager operation and
we can prioritize our command over anything else that may be interacting with
the package manager.

(cherry picked from commit 01962f6)

Co-authored-by: Cas Donoghue <[email protected]>
donoghuc added a commit that referenced this pull request Apr 29, 2025
@mergify @donoghuc
Make redhat exhaustive test install command more robust (#17592) (#17604
a2a2e45 
)

We are seeing a frequent issue in CI where tests are failing to install via
package manager on rhel8. It looks like the issue may be due to processes that
are being terminated and leaving behind lock files on the rpm database. This
commit udpates the install method to try to do a database rebuild routine which
will force lock files to be removed. This fix assumes that at the time of
testing, our tests should take priority over any package manager operation and
we can prioritize our command over anything else that may be interacting with
the package manager.

(cherry picked from commit 01962f6)

Co-authored-by: Cas Donoghue <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@kaisecheng kaisecheng kaisecheng approved these changes

Assignees

No one assigned

Labels

backport-active-all Automated backport with mergify to all the active branches

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@donoghuc @elasticmachine @kaisecheng