-
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
[CI] Add E2E for x-pack/elastic-agent (fleet) #24112
Conversation
/test |
@mdelapenya , I might need some help here, the packaging finished as expected but I see a couple of issues:
While the target for this PR was the master branch, and artifacts were uploaded correctly: The e2e logs can be found here and I don't see any references to the 7.10.3 branch :/, the below stacktrace is the header of the above build output:
any hints? |
As discussed online, it seems the nightly tests (for the upgrade of the elastic-agent) are being executed, which is something we should not do for PRs. On the other hand, there are CI jobs that are already executing these tests on a nightly basis, so I think we are covered for branches. Our solution is to always call the fleet entrypoint for this feature excluding the |
/test |
I just mocked the functional-test make goal and it returned the errorlevel as expected
Maybe there is something with the pipeline 2.0 |
* upstream/master: [Elastic Agent] Fix docker entrypoint for elastic-agent. (elastic#24155) [PACKAGING] Push docker images with the architecture in the version (elastic#24121) [Agent] Add agent standalone manifests for system module & Pod's log collection (elastic#23938) indicator type url is in upper case (elastic#24152) [Filebeat] Document netflow internal_networks and set default (elastic#24110) [Filebeat] Adding fixes to the TI module (elastic#24133) [Enhancement] Add RotateOnStartup feature flag for file output (elastic#19347) [Ingest Manager] Fix: Successfully installed and enrolled agent running standalone (elastic#24128) Set Elastic licence type for APM server Beats update job (elastic#24122) Add logrotation section on Running Filebeat on k8s (elastic#24120) [CI] Run if manual UI (elastic#24116) [CI] enable x-pack/heartbeat in the CI (elastic#23873)
Indeed! b53ae70 should be the way |
@Mergifyio update |
Command
|
* upstream/master: (658 commits) Add complete k8s metadata through composable provider (elastic#27691) Revert "Fix issue where --insecure didn't propogate to Fleet Server ES connection (elastic#27969)" (elastic#27997) Remove deprecated kafka fields (elastic#27938) [Filebeat] Add Base64 encoded HMAC & UUID template functions to httpjson input (elastic#27873) Improve httpjson template function join (elastic#27996) Remove kubernetes.container.image alias (elastic#27898) [Elastic Agent] Golden files for program tests (elastic#27862) [Elastic Agent] Disable modules.d in metricbeat (elastic#27860) libbeat/common/seccomp: provide default policy for linux arm64 (elastic#27955) Fix logger statement in aws-s3 input (elastic#27982) Fix wrong merge (elastic#27976) Fix issue where --insecure didn't propogate to Fleet Server ES connection (elastic#27969) Forward-port 7.14.2 changelog to master (elastic#27975) [Filebeat] Removing duplicate modules (aliases) Observability (elastic#27919) Fix path in vagrant windows script (elastic#27966) [Filebeat] Removing duplicate modules (aliases) and Cyberark (elastic#27915) No changelog for 8.0.0-alpha2 (elastic#27961) Add write access to 'url.value' from 'request.transforms'. (elastic#27937) Docker: remove deprecated fields (elastic#27933) Filebeat: Make all filesets disabled in default configuration (elastic#27762) ...
This pull request does not have a backport label. Could you fix it @v1v? 🙏
NOTE: |
/test |
Whats the update on this? Can we get this merged soon? |
The e2e tests are stalled and therefore killed, see the logs For clarity, this stage triggers -> https://github.com/elastic/e2e-testing/blob/master/.ci/scripts/fleet-test.sh. @mdelapenya , any hints why the tests are slow and get killed? |
After discussing with Manu offline, it's required to support a different way to run those E2E tests since the entrypoint runs the script but it runs sequentially rather than in parallel, therefore it takes ages. I'm gonna work to support to trigger a job, actually the e2e job for fleet. This should provide faster feedback. |
* upstream/master: (73 commits) Remove GCP support from Functionbeat (elastic#28253) Move labels and annotations under kubernetes.namespace. (elastic#27917) Update go release version 1.17.1 (elastic#27543) Osquerybeat: Runner and Fetcher unit tests (elastic#28290) Osquerybeat: Improve handling of osquery.autoload file, allow customizations (elastic#28289) seccomp: allow clone3 syscall for x86 (elastic#28117) packetbeat/protos/dns: don't render missing A and AAAA addresses from truncated records (elastic#28297) [7.x] [DOCS] Update api_key example on elasticsearch output (elastic#28288) [cloud][docker] use the private docker namespace (elastic#28286) Update aws-lambda-go library version to 1.13.3 (elastic#28236) Deprecate common.Float (elastic#28280) Filebeat: Change compatibility test stage to test against previous minor instead of 7.11 (elastic#28274) x-pack/filebeat/module/threatintel/misp: add support for secondary object attribute handling (elastic#28124) Explicitly pass http config to doppler consumer (elastic#28277) processors/actions/add_fields: Do not panic if event.Fields is nil map (elastic#28219) Resolved timestamp for defender atp (elastic#28272) [Winlogbeat] Tolerate faults when Windows Event Log session is interrupted (elastic#28191) [elastic-agent] proxy requests to subprocesses to their metrics endpoints (elastic#28165) Build cloud docker images for elastic-agent (elastic#28134) Upgrade k8s go-client library (elastic#28228) ...
/test |
/test |
Status updateThe e2e testing for the elastic-agent is now in place, and a particular GitHub check is created: Though, I discussed offline with @adam-stokes and we thought to enable the e2e testing in incremental stages, then we can initially provide a subset of what the fleet-server/elastic-agent e2e scenarios are in place and then add incrementally more scenarios, this will avoid having any kind of flakiness if we move forward with this approach. Short story, elastic/e2e-testing#1648 allows to configure those scenarios/suites in files, but need to agree with the rest of the team. |
(cherry picked from commit a2fde72)
(cherry picked from commit a2fde72)
(cherry picked from commit a2fde72) Co-authored-by: Victor Martinez <[email protected]>
(cherry picked from commit a2fde72) Co-authored-by: Victor Martinez <[email protected]>
* upstream/7.x: chore: use same branching schema for e2e (#28493) [Automation] Update elastic stack version to 7.16.0-8bf0b9b1 for testing (#28484) chore(ci): remove not used param when triggering e2e tests (#27823) (#27828) Add deprecation warning for filebeat disabled modules (#28393) Run Python tests in libbeat (#28438) (#28485) Register `storage_account` as second name for `storage` metricset (#28447) (#28470) [CI] Add E2E for x-pack/elastic-agent (fleet) (#24112) (#28465)
What does this PR do?
e2e
stage within the main pipeline using the e2e pipeline job in addition to running the script if needed.x-pack/elastic-agent
e2e
pipeline in order to benefit from the parallelisationWhy is it important?
As requested by the team.
Important
There are e2e test failures ...
Issues
Requires elastic/e2e-testing#793
Follow up
Refactor the calls to the e2e pipeline/jobs with same shared library step.