-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Ingest Manager] Elastic Agent - Endpoint e2e test fix #23776
[Ingest Manager] Elastic Agent - Endpoint e2e test fix #23776
Conversation
Pinging @elastic/agent (Team:Agent) |
Pinging @elastic/ingest-management (Team:Ingest Management) |
/Package |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
Test | Results |
---|---|
Failed | 0 |
Passed | 5846 |
Skipped | 16 |
Total | 5862 |
@michalpristas Can you clarify the description of this PR, is that working at intended? is there a bug with endpoint? |
This must have to do with the switch to go 1.15. Some reason the certificate generation changes that cause endpoint to stop connecting. I would be surprised this was a change on the Endpoint side. |
@ph i think it's something related to gdpr library, they use one from google. i was asking in a channel but so far no response about how to gather details or anything helpful endpoint side. |
/Packaging |
Thanks @michalpristas for the clarification, I think @blakerouse is right here concerning the 1.15 changes. |
/packaging |
1 similar comment
/packaging |
What does this PR do?
This PR uses CN together with DNSName,
in nightly test we see that when agent is assigned an Endpoint Security integration it wont show up in Security App.
I was not able to get more info from Endpoint so far but what i see is a message
AgentComms.cpp:628 Waiting for GRPC connection to be READY
for. really long period of time.Agent wise we are not experiencing any errors,
Creds endpoint created a LISTENING
I see endpoint connecting to Creds endpoint and not issues there server side.
But when i change generated cert to have CN as addition to DNSNames, endpoint is ready in 20s and Endpoint reported green, showing up in security tabs. I did multiple runs, mutiple build always same behavior.
I suspect gdpr library to do some checks on CN so while golang stopped supporting CN and we moved to DNSNames we probably need to keep CN for a while
Why is it important?
#23693
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.