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.

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

Fix the FileAudit test in CTS for systemd systems #3809

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Fix the FileAudit test in CTS for systemd systems #3809

wants to merge 2 commits into from

Conversation

clumens
Copy link
Contributor

@clumens clumens commented Jan 23, 2025

After:

Jan 23 16:25:27 Cluster nodes:
Jan 23 16:25:27 * rhel9-ctslab-1
Jan 23 16:25:27 * rhel9-ctslab-2
Jan 23 16:25:27 * rhel9-ctslab-3
Jan 23 16:25:31 Warning: Core file on rhel9-ctslab-1: Thu 2025-01-23 16:25:03 EST 834 0 0 SIGSEGV none /root/crash -
Jan 23 16:25:33 Audit FileAudit FAILED.

@clumens
Refactor: python: Reduce code duplication looking for core dumps.
e05d2ad
@clumens
Low: python: Use coredumpctl to check for core files.
edb2f5a 
If we're running on a system that supports systemd, core dumps will be
managed using coredumpctl.  We need to use that tool to figure out if
there are any core dumps instead of looking in various directories.

Unfortunately, this also means we won't know whether a pacemaker-related
tool wrote a core dump or not.  They'll all be in the journal by binary
name, which means we would have to search for every pacemaker or
corosync binary possible.

However, it seems likely that ctslab is being run on a dedicated system
and so if there are any core dumps present, they likely came from
pacemaker or something it relies upon.  So it's probably fine to just
check for any core dumps and warn if one is found.

Fixes T651
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@clumens