Add a standalone test scenario for fleet server mode#978
Add a standalone test scenario for fleet server mode#978adam-stokes merged 1 commit intoelastic:masterfrom
Conversation
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Test errors
Expand to view the tests failures
|
| Test | Results |
|---|---|
| Failed | 2 |
| Passed | 136 |
| Skipped | 0 |
| Total | 138 |
Genuine test errors 
💔 There are test failures but not known flaky tests, most likely a genuine test failure.
- Name:
Initializing / End-To-End Tests / ubuntu-18.04_fleet_backend_processes / Un-installing the installed centos agent – Backend Processes - Name:
Initializing / End-To-End Tests / ubuntu-18.04_fleet_stand_alone_agent / Deploying a default stand-alone agent with fleet server mode – Stand-alone Agent
|
I think this could solve #958 as well? We want to move toward having the ability for the cli to easily run scenarios the CI would do. Currently running |
This should be handled by:
|
|
I am on holiday until Thursday, but I think that test failures are legitimate and this merge should be reverted. |
(cherry picked from commit 83ace74)
(cherry picked from commit 83ace74)
(cherry picked from commit 83ace74)
|
I added the labels too fast, without reading #978 (comment). Let's not merge those backports until the fix is done. |
…#978) (elastic#987)" This reverts commit a42c0ce.
…#978) (elastic#988)" This reverts commit 601064a.
What does this PR do?
Starts Elastic Agent with Fleet Server and auto-enroll.
There seems to be an issue with https://github.com/elastic/e2e-testing/compare/master...jalvz:fleet-server-standalone?expand=1#diff-a6c6a3ad6fe70a90f2f59acfe75e589cd5aa7ca78361c2e26472bd2d0bb4f44eL15, removing that line the Agent enrolls correctly.
With that line, the error looks like:
/usr/share/elastic-agent/elastic-agent.yml: rename /usr/share/elastic-agent/elastic-agent.yml /usr/share/elastic-agent/elastic-agent.yml.2021-03-31T14-16-29.6932.bak: device or resource busyNot sure what that is.
For reference, the following also works:
docker run --network fleet_default -e KIBANA_HOST=http://kibana:5601 -e KIBANA_USERNAME=elastic -e KIBANA_PASSWORD=changeme -e KIBANA_FLEET_SETUP=1 -e FLEET_SERVER_ENABLE=1 -e FLEET_SERVER_INSECURE_HTTP=1 -e FLEET_SERVER_HOST=0.0.0.0 -p 8220:8220 docker.elastic.co/beats/elastic-agent:8.0.0-SNAPSHOTWhy is it important?
Required for upcoming tests
Checklist
make noticein the proper directory)Related issues
Related to #900