-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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] RepositoryAzureClientYamlTestSuiteIT, AzureRepositoriesMeteringIT, AzureSearchableSnapshotsIT, AzureStorageCleanupThridPartyTests failing #107753
Comments
Pinging @elastic/es-distributed (Team:Distributed) |
And a similar failure for AzureStorageCleanupThridPartyTests on 8.14: https://gradle-enterprise.elastic.co/s/dalel5inn6nfi |
8.13 also affected: https://gradle-enterprise.elastic.co/s/dsunqlvt5dxmc |
Got another on main: https://gradle-enterprise.elastic.co/s/bc6cvshdeim7k |
And another on 8.14: https://gradle-enterprise.elastic.co/s/orhkaur67t7xw |
According to history, it started to fail quite recently |
Several more failures today:
I'm reluctant to mute whole test suites, but this is causing incredible noise and I see AzureStorageCleanupThridPartyTests has been already muted. I'll let @elastic/es-distributed decide what to do. |
It looks like we need to rotate the SAS token used for integration tests |
Seems like authentication against Azure failed. Multiple tests and test suites are affected.
Build scan:
https://gradle-enterprise.elastic.co/s/jl746rixjgqq4/tests/:modules:repository-azure:yamlRestTest/org.elasticsearch.repositories.azure.RepositoryAzureClientYamlTestSuiteIT/test%20%7Byaml=repository_azure%2F20_repository%2FRegister%20a%20repository%20with%20a%20non%20existing%20client%7D
Reproduction line:
Applicable branches:
main, 8.14, 8.13, 7.17
Reproduces locally?:
Didn't try
Failure history:
Failure dashboard for
org.elasticsearch.repositories.azure.RepositoryAzureClientYamlTestSuiteIT#test {yaml=repository_azure/20_repository/Register a repository with a non existing client}
Failure excerpt:
The text was updated successfully, but these errors were encountered: