-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Failing test: X-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/security_and_spaces/tests/alerting/disable·ts - alerting api integration security and spaces enabled Alerts disable space_1_all at space2 should still be able to disable alert when AAD is broken #84007
Comments
Pinging @elastic/kibana-security (Team:Security) |
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
|
Yikes! a 409 in the alerting code resulted in a 500 being returned from an alerting endpoint. Not good. So, probably two bugs to fix here, whatever caused the 500 needs to be fixed first. And I thought we had code that would retry conflicts like this, so that we shouldn't be sending 409's back through the http endpoints. My guess is that is is the retry logic that is causing the 500's. And that there should be tests for this, but maybe there aren't, or if we do have some, they are insufficient. |
New failure: Jenkins Build |
A test failed on a tracked branch
First failure: Jenkins Build
The text was updated successfully, but these errors were encountered: