-
Notifications
You must be signed in to change notification settings - Fork 282
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
[BUG] SecuritySSLReloadCertsActionTests is using outdated certificates #2675
Comments
stephen-crawford
added
bug
Something isn't working
untriaged
Require the attention of the repository maintainers and may need to be prioritized
labels
Apr 12, 2023
stephen-crawford
changed the title
[BUG] Tenancy changes break CI--
[BUG] Tenancy changes break CI
Apr 12, 2023
@scrawfor99 It's not related to the tenancy changes. Some of the certificates used in
|
Certs were updated in opendistro-1.13 for these tests. Details for generating new certs can be found here: #1943 (comment) |
cwperks
changed the title
[BUG] Tenancy changes break CI
[BUG] SecuritySSLReloadCertsActionTests is using outdated certificates
Apr 12, 2023
3 tasks
stephen-crawford
added
triaged
Issues labeled as 'Triaged' have been reviewed and are deemed actionable.
and removed
untriaged
Require the attention of the repository maintainers and may need to be prioritized
labels
Apr 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the bug?
The recent tenancy changes have broken all builds. When CI tries to run, it eventually fails on the
TransportUserInjectorIntegTest
,TenancyMultitenancyEnabledTests
, and others. This behavior can be seen in PR's which make no code changes such as #2660 which shows the change is part of the existing code base.How can one reproduce the bug?
Steps to reproduce the behavior:
Run any builds on the GitHub runners.
What is the expected behavior?
Runners should pass by default and only fail when a PR is introducing a new issue.
Do you have any additional context?
The tenancy feature was recently modified as part of #2607. This is likely the cause.
The text was updated successfully, but these errors were encountered: