-
Notifications
You must be signed in to change notification settings - Fork 42
Add support for Debian 11 and Ubuntu 22.04 platforms #2603
Conversation
This pull request does not have a backport label. Could you fix it @narph? 🙏
|
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
|
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.
This looks good to me, although we need one more thing, as described in https://github.com/elastic/e2e-testing/pull/2589/files#diff-53b78ab29e8f8423188da6c0806aaa9de90d39bd3502d83a655a1a68429fcfe2R43, which is to actually run the desired scenarios in the new platforms
@@ -5,51 +5,51 @@ SUITES: | |||
scenarios: |
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.
I think we want to include debian11 and ubuntu in the nightly builds. So I guess they should be added in this file too.
@jlind23 could you confirm?
@@ -5,54 +5,54 @@ SUITES: | |||
scenarios: |
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.
This file is mainly used by the test framework while developing it. The other descriptors are used by downstream jobs: Beats, Agent, Nightly...
This pull request is now in conflict. Could you fix it @narph? 🙏
|
@narph I'm seeing the very same error while creating all the new instances for Debian 11 and Ubuntu:
Will fetch this PR locally and run it from local using the build scripts. Will ping you here with my investigation about that issue |
@narph I replaced current Ubuntu AMI with the one provided by AWS as a Quickstart AMI and the creation works: I'm currently running a few scenarios on that Ubuntu to check it. If it works, I will push a commit to this branch with the changes. Same for Debian 11. |
For Debian, I'm checking their website for the AMIs: https://wiki.debian.org/Cloud/AmazonEC2Image/Bullseye, where they say that I do not know why I'm not able to discover that AMI ID in the AWS console 🤷 Anyway. I checked locally and I'm able to create a node with that AMI, successfully running the test scenarios on it 🚀 |
Ok, this is working now. There are two failures that I'd recommend to investigate before merging, as they affect Debian 11: make -C .ci setup-stack # it will fail as the fleet-server needs a different healthcheck for Kibana + Fleet
make -C .ci recreate-fleet-server # causes the stack to restart fleet-server
make -C .ci provision-node NODE_IMAGE=ami-0c7c4e3c6b4941f0f NODE_LABEL=debian_11_amd64
make -C .ci setup-node NODE_IMAGE=ami-0c7c4e3c6b4941f0f NODE_LABEL=debian_11_amd64
make -C .ci run-tests TAGS="backend_processes" NODE_LABEL=debian_11_amd64
make -C .ci run-tests TAGS="system_integration" NODE_LABEL=debian_11_amd64 |
I see there are the same flaky tests, the Debian 11 tests just passed. Can you confirm? |
Yes, it's seems the debian/Ubuntu support is at the same level than the rest of platforms. LGTM |
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.
Ready!! 🚀
…port * upstream/main: Add support for Debian 11 and Ubuntu 22.04 platforms (elastic#2603) fix: retire 8.1 snapshot from upgrades (elastic#2616)
* main: Add support for Debian 11 and Ubuntu 22.04 platforms (elastic#2603) fix: retire 8.1 snapshot from upgrades (elastic#2616) bump stack version 8.4.0-42ce0eef (elastic#2613) docs: document AWS requirements (elastic#2589) chore: move elastic-agent's k8s-autodiscover scenarios from beats to elastic-agent profile (elastic#2601)
* main: (22 commits) chore(jjbb): increase build timeout to 2h (elastic#2661) chore: increase build timeout to 2h (elastic#2660) feat: run tests on windows 2019 (elastic#2468) Remove aws instance reaper Jenkins job (elastic#2647) Update k8s version to v1.24 (elastic#2644) chore: simplify extracting info from the supported platforms (elastic#2637) ci: avoid running on branches that are not available anymore (elastic#2627) Add support for Debian 11 and Ubuntu 22.04 platforms (elastic#2603) fix: retire 8.1 snapshot from upgrades (elastic#2616) bump stack version 8.4.0-42ce0eef (elastic#2613) docs: document AWS requirements (elastic#2589) chore: move elastic-agent's k8s-autodiscover scenarios from beats to elastic-agent profile (elastic#2601) Add test scenario for elastic agent tags (elastic#2552) bump stack version 8.4.0-3525aaf7 (elastic#2597) bump stack version 8.4.0-df27a645 (elastic#2591) fix: agent directories must belong to root (elastic#2590) chore: bump maintenance versions in mergify (elastic#2563) chore: bump kubernetes versions (elastic#2562) fix: use fixed, valid version for protobuffers (elastic#2569) chore: do not run apm-server helm chart scenarios for Beats (elastic#2564) ...
- suite: "fleet" | ||
scenarios: | ||
- name: "Fleet" | ||
tags: "fleet_mode_agent" | ||
platforms: ["centos8_arm64", "centos8_amd64", "debian_arm64", "debian_amd64", "sles15"] | ||
platforms: ["centos8_arm64", "centos8_amd64", " debian_10_arm64", "debian_10_amd64", "sles15"] |
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.
@v1v we found it! 🤦
What does this PR do?
Adds support for Debian 11 and Ubuntu 22.04 platforms
Why is it important?
Adds support for Debian 11 and Ubuntu 22.04 platforms.
Latest Debian and Ubuntu versions are already supported for other stack components and customers are asking if we support it as well.
We need to make sure elastic agent/fleet server tests will pass on these 2 platforms as well.
Checklist
make unit-test
), and they are passing locallymake notice
in the proper directory)Related issues