-
Notifications
You must be signed in to change notification settings - Fork 68
Conversation
* adapt setup to changes from elastic/beats#24220
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪 |
There are a couple of lines too long
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what about FLEET_URL? wasn't that one required (even if pointing to Kibana)?
"FLEET_ENROLL": "1", | ||
"FLEET_SETUP": "1", | ||
"FLEET_SERVER_POLICY_NAME": "Default policy", # TODO(simitt): make configurable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh, are you sure it is "Default policy" and not "Default"?. i hope this would not be needed anyways
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it is Default policy
; and I already put up elastic/beats#24385 to get rid of this config, but no review yet.
Not required, it is actually only used if |
Co-authored-by: Ivan Fernandez Calvo <[email protected]>
Sorry for the noise on this PR - the |
…rt-from-build * upstream/master: (24 commits) Add mergify (elastic#1089) fix: update flake8 and deps to work with Python 3.8+ (elastic#1085) chore: bump elastic stack (elastic#1087) fix: force to activate venv (elastic#1086) fix: --opbeans-node-agent-local-repo=/a/local/dir (elastic#1084) ci: jjbb remove periodic-folder-trigger (elastic#1079) Fix APM Server managed by Elastic Agent setup (elastic#1078) docker/opbeans/go: use -mod=mod (elastic#1077) [fleet] fix elastic-agent setup (elastic#1076) update supported stack versions (elastic#1075) [CI] Increase timeout (elastic#1070) Add --package-registry-url flag (elastic#1069) Create opbeans_user/role with write/read access for the opbeans-python (elastic#1063) reset postgres sequences after database migration (elastic#1062) chore: bump Elastic Stack (elastic#1060) docker/go/nethttp: go build -mod=mod (elastic#1061) check agent liveness via version subcommand (elastic#1059) test: use filebeat step to grab Docker logs (elastic#1029) Update dotnet sdk 5.0 docker image (elastic#1048) docs: using Dyno (elastic#1056) ...
What does this PR do?
Since recent changes of running Fleet Server when starting Elastic Agent (elastic/beats#24220) the elastic-agent setup was broken. This PR fixes the setup as far as possible.
There is one more change that needs to be merged into Kibana elastic/kibana#92422; until this PR is merged, the Elastic Agent enrollment endlessly waits for the policy to be written by Kibana. One should see the following log line in the Fleet server logs:
{"message":"Waiting on policy with Fleet Server integration: d5204d20-7fee-11eb-9337-e79c33f6692e"}
Why is it important?
To be able to run with Elastic Agent again.