-
Notifications
You must be signed in to change notification settings - Fork 16
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
Agent install tests failing on main
#277
Comments
Same error seen running tests against |
@cmacknz this looks like Fleet attempts enrollment perpetually, which stops it from responding to the service manager? |
perhaps related to elastic/elastic-agent#4800 which was backported to 8.14 |
Yes that would be because of elastic/elastic-agent#4727 if we are using --delay-enroll. The actual root cause is the enrollment is failing. |
We are trying to enroll with a non-existent host? {"log.level":"error","@timestamp":"2024-06-20T13:05:10.936Z","log.origin":{"file.name":"cmd/run.go","file.line":565},"message":"failed to perform delayed enrollment (will try again): fail to enroll: fail to execute request to fleet-server: lookup placeholder: no such host","log":{"source":"elastic-agent"},"ecs.version":"1.6.0"} |
Yes, this should not prevent stopping or removal of Elastic Agent as this will be a common scenario post-deployment. I cannot stop the service or uninstall the agent via the MSI or the elastic-agent binary once the service has started but enrollment is retrying I believe this is an agent bug not related to the MSI |
…#289) Backport of #287 This PR adds an alternate step in the elastic-stack-installers that the Independent Agent Release will use in order to get only the Elastic Agent windows installer (.msi) built. The new pipeline step uses a new script that does the following: Retrieve the MSI artifacts from the Build step Moves the MSI artifacts to a new directory Creates a .sha512 file for the MSI file Saves the MSI and .sha512 artifacts using Buildkite's built-in upload functionality Sets metadata in the calling pipeline if the TRIGGER_JOB_ID is set The calling pipeline will then use this metadata to download the saved artifacts Merged, bypassing checks due to #277
Seen in https://buildkite.com/elastic/elastic-stack-installers/builds/5429#01903577-fb5d-45f5-8f2f-2ca2bf7a942e via an unrelated PR: #276
Error:
Link to CI logs: https://buildkite.com/elastic/elastic-stack-installers/builds/5429#01903577-fb5d-45f5-8f2f-2ca2bf7a942e/3842-4533
The text was updated successfully, but these errors were encountered: