-
Notifications
You must be signed in to change notification settings - Fork 24.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] MlJobIT#testDeleteJobAfterMissingAliases fails #32034
Comments
Pinging @elastic/ml-core |
Line 448 on the test is:
How could that throw |
It's the age-old problem about security changing the behaviour of some endpoints. One such endpoint is It can be demonstrated as follows:
This is extremely unlikely to affect any customer, as anyone creating an ML job probably has at least one other index. But possibly what we should do is wait for the job results index to exist before returning from creating a job. This would give a more consistent end-user experience - the instant create job returns you could safely search the job results index without risk of an exception. I assume the reason this bug has surfaced now is that creating an index on a multi-node cluster takes longer than on a single node cluster so it's another side-effect of switching the native tests to a 3 node cluster. |
Another instance in 6.x: |
Failure: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+intake/2315/console
This doesn't reproduce locally:
Error:
The text was updated successfully, but these errors were encountered: