-
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
[Fleet] Elastic-Agent doesn't start up with .rpm / .deb usage (with enroll cmd) #21200
Comments
Pinging @elastic/ingest-management (Team:Ingest Management) |
I wouldnt be surprised that debian is also broken. The package generation is quite similar between the two using fpm. |
here is what I did to get started: from history output: Here is what systemctl says after doing the install and enroll. [zeus@mainqa-atlcolo-10-0-6-45 ~]$ ls Sep 18 15:51:34 mainqa-atlcolo-10-0-6-45.eng.endgames.local systemd[1]: elastic-agent.service: Failed with result 'exit-code'. here is a ps call that returns nothing: here is the log after the enroll call, just the one line: and there is no action store file at: And I tried running the .tar.gz on a host and it worked, and then I un-installed it and used the .rpm and started it up and find the same as the above (so I know the host should be ok). |
@blakerouse is this still an issue? |
I can hit this today to verify on 7.10 BC2 build. |
And I can confirm - with the QAS team's help, the 7.10 BC2 is indeed still in need of some fixing for the .rpm / .deb installs |
this is awesome, thanks Blake. @rahulgupta-qasource I'll pass a note in the daily email to discuss testing. Thanks! |
Bug Conversion: Below 01 Testcase already exists for this ticket: |
I need to put details in... I can grab what logs do exist. But during the weekly sync we realized this wasn't logged so I'm dropping a ticket in. Tested with 8.0
The e2e-testing work is finding this bug:
edavis$ OP_LOG_LEVEL=TRACE DEVELOPER_MODE=true ELASTIC_AGENT_USE_CI_SNAPSHOTS=false ELASTIC_AGENT_VERSION=8.0.0-SNAPSHOT godog -t "endpoint-policy-check"
manual testing finds the same. linux .tar.gz is working fully.
The text was updated successfully, but these errors were encountered: