-
Notifications
You must be signed in to change notification settings - Fork 22
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
Test failure of Auditbeat on Suse and SLES #115
Comments
cwurm
pushed a commit
to elastic/beats
that referenced
this issue
Apr 5, 2019
Both openSUSE and SLES use RPM under the hood, so we can use the code we already have for CentOS/Fedora. Depends on #11628. Fixes elastic/beats-tester#115.
cwurm
pushed a commit
to cwurm/beats
that referenced
this issue
Apr 5, 2019
Both openSUSE and SLES use RPM under the hood, so we can use the code we already have for CentOS/Fedora. Depends on elastic#11628. Fixes elastic/beats-tester#115. (cherry picked from commit ebdf66d)
cwurm
pushed a commit
to cwurm/beats
that referenced
this issue
Apr 5, 2019
Both openSUSE and SLES use RPM under the hood, so we can use the code we already have for CentOS/Fedora. Depends on elastic#11628. Fixes elastic/beats-tester#115. (cherry picked from commit ebdf66d)
cwurm
pushed a commit
to elastic/beats
that referenced
this issue
Apr 7, 2019
Cherry-pick of PR #11634 to 7.0 branch. Original message: Both openSUSE and SLES use RPM under the hood, so we can use the code we already have for CentOS/Fedora. Depends on #11628. Fixes elastic/beats-tester#115.
cwurm
pushed a commit
to elastic/beats
that referenced
this issue
Apr 7, 2019
Cherry-pick of PR #11634 to 6.7 branch. Original message: Both openSUSE and SLES use RPM under the hood, so we can use the code we already have for CentOS/Fedora. Depends on #11628. Fixes elastic/beats-tester#115.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The package dataset fails and then Auditbeat doesn't start.
@cwurm Should we just not configure those operating systems with the package dataset? Or would the dataset work on these systems if it got passed the OS family check? Ansible classifies these as being in the
suse
family (so not debian or redhat), and go-sysinfo doesn't classify them at all right now. I think they use Zypper, for package management, but they might also have librpm available.https://beats-ci.elastic.co/job/elastic+beats-tester+master/382/
The text was updated successfully, but these errors were encountered: