-
Notifications
You must be signed in to change notification settings - Fork 42
Update .e2e-tests.yaml to add windows srv 2022 #2023
Conversation
This pull request does not have a backport label. Could you fix it @jlind23? 🙏
|
🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
@mdelapenya it seems to be the same test failing on each PR. Can we fix it? |
The windows stage did fail: https://beats-ci.elastic.co/blue/organizations/jenkins/e2e-tests%2Fe2e-testing-mbp/detail/PR-2023/1/pipeline, @adam-stokes is looking into it. And for the existing failure, there is an open issue, but I think it's not related to the tests but to the elastic-agent container. Please more details here: #1992, which links to elastic/beats#29811 as root cause |
@adam-stokes @mdelapenya anything I can do here on my end? |
This requires a bit more work to support it in ansible, I'll need to get some additional tasks written to support winrm etc |
@adam-stokes Should I close it for now? I also wanted to add Windows 11 but i'm quite sure I am going to face the same issue right? |
This pull request is now in conflict. Could you fix it @jlind23? 🙏
|
@jlind23 I'd leave it open, I'll reference it when I can complete the work |
@adam-stokes any update there? |
This pull request is now in conflict. Could you fix it @jlind23? 🙏
|
@adam-stokes Could you please update this issue with the latest status? Please let me know if we need to reflect the work that needs to be done here in our sprint planning if it isn't already. Let's try to get @jlind23 unblocked if we can. :) |
@cachedout is there any progress that can be shared here? |
@jlind23 We had to move @adam-stokes over to a more urgent project temporarily. I don't think there's any news to share on this at the moment, unfortunately. |
I'm going to close this one in favour of #2338, which I've started a local branch for it Please reopen if you have any consideration about it |
Add Windows server 2022 as an operating system on which fleet server and elastic agent tests will be deployed.