-
Notifications
You must be signed in to change notification settings - Fork 144
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
[SLES 15]: No "system.auth" logs for system integration under Data Streams tab for SLES 15 linux agent. #4495
Comments
Pinging @elastic/fleet (Team:Fleet) |
@manishgupta-qasource Please review. |
Reviewed & Assigned to @fearful-symmetry |
The auth module tends to depend a lot on system configuration. Have we confirmed that:
|
Hi @fearful-symmetry
Build details: Logs: Please let us know if anything else is required from our end. |
I don't see any errors in the logs. Can we verify if:
|
hi - sorry I missed this, even 7 days ago, but I'm not certain SLES 15 is going to be cited as supported. Let's hold off until we get that decision. Our original manual test was a fact finding mission, here is a good fact to consider. We can ask the leadership group to confirm and circle back. Having said that, I would prefer to run the same test of versions against one of our confirmed supported OSes to see, like a CentOS or Debian distro. If it is reproduced there, I'd log a separate bug to make it clear - but we can link them, in case any logging / info here is helpful. @amolnater-qasource @dikshachauhan-qasource we don't need to do any SLES 15 tests further until confirmed, except to test other OSes for potential bugs that may actually be evidenced elsewhere. |
Hi @fearful-symmetry @EricDavisX thanks for the update, we will hold our testing on SLES 15 till further confirmation. Please let us know if anything else is required from our end. |
Seconded. |
Hi @EricDavisX Observations:
Build details: Please let us know if anything else is required from our end. |
Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as |
Hi @fearful-symmetry @EricDavisX, We have re-validated this issue on the latest 8.6.0 BC8 Kibana Staging environment and found the issue is still reproducible. Build details:
Below are the observations:
Screenshots: Please let us know if we are missing anything. Thanks! |
We have observed that this issue is still reproducible and occuring on 8.5 BC5 build. Observations:
Build details:
Please let us know if we are missing anything. Thanks! |
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
@dikshachauhan-qasource can you attach agent diagnostics from when this problem was most recently reproduced? |
Hi @cmacknz Please find the required daignostics log in attached zip folder reproduced today on below build details. Build details:
Logs: Thanks |
Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as |
Hi Team, We have revalidated this issue on latest 8.14.0 Snapshot kibana cloud environment and found it still reproducible on SLES 15. Observations:
Build details: Agent Logs: Please let us know if anything else is required from our end. |
JFI @pierrehilbert |
For me this is the same case than #3650 will be covered when elastic/beats#37086 will be done. |
Kibana version: 7.15.0 BC-2 Kibana cloud environment
Host OS and Browser version: All, All
Build details:
Preconditions:
Steps to reproduce:
System
from Integration dropdown andlogs
from type dropdown.Logs:
logs.zip
Expected Result:
"system.auth" logs should be generated for system integration under Data Streams tab for SLES 15 agent.
Screenshot:
Note:
This issue is not observed for Ubuntu 20 machines with .tar artifact.
The text was updated successfully, but these errors were encountered: