-
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] AzureStorageCleanupThirdPartyTests failing, possibly needs new set of credentials #84231
Comments
This looks very similar to #75648, I'll see if I can open a similar issue for Infra to solve this. |
Pinging @elastic/es-distributed (Team:Distributed) |
I opened https://github.com/elastic/infra/issues/34818 on the Infra side to see if they can check if this is indeed related to problems with old credentials. |
These are probably also related, but the error looks slightly different: https://gradle-enterprise.elastic.co/s/euqoyry4qsqlq/console-log?task=:plugins:repository-azure:azureThirdPartyTest
The error code in the nested exception is slightly different and it doesn't mention 'AuthorizationPermissionMismatch'. The other build before is a "SAS" build, whatever that might mean to anybody. |
@fcofdez are you still having trouble updating these credentials? Do we need to reach back out to infra? |
I've just updated the credentials, I'll keep an eye and close the issue once I verify that the suite is green again. |
There has been some more |
That's strange, I'll take another look |
Another case here - https://gradle-enterprise.elastic.co/s/ekxpusn6yj2cg |
Possibly related failure in The Azure response contains: |
Tests failed due to the missing repo, diggin in the logs I saw many instances of |
Sorry about the noise here, I thought that only sas tokens were expired. I renewed the regular keys too. The tests should pass now. |
@fcofdez here is another failure. I am going to assume it doesn't have your commit fix yet in the build since that was merged so recently: https://gradle-enterprise.elastic.co/s/7s5v7fssadiam/console-log?task=:plugins:repository-azure:azureThirdPartyTest |
Let me take another look @benwtrent, it's a credentials issue |
I regenerated the SAS token and the tests pass locally, I'll keep an eye for failures on CI |
@fcofdez there is another failure that looks a lot like this issue: https://gradle-enterprise.elastic.co/s/qpf6oknyatqb2/console-log?task=:x-pack:plugin:repositories-metering-api:qa:azure:integTest |
CI Link
https://gradle-enterprise.elastic.co/s/sevrq5jszpe3w
Repro line
./gradlew ':plugins:repository-azure:azureThirdPartyTest' --tests "org.elasticsearch.repositories.azure.AzureStorageCleanupThirdPartyTests.testListChildren" \ -Dtests.seed=203404662522F345 \ -Dtests.locale=de-CH \ -Dtests.timezone=Europe/Podgorica \ -Druntime.java=8
Does it reproduce?
Didn't try
Applicable branches
7.17, 8.0, 8.1
Failure history
Several failures today
Failure excerpt
org.elasticsearch.repositories.azure.AzureStorageCleanupThirdPartyTests > testListChildren FAILED
RepositoryVerificationException[[test-repo] path [7.17_third_party_tests_203404662522F345] is not accessible on master node]; nested: BlobStorageException[Status code 403, "
AuthorizationPermissionMismatch
This request is not authorized to perform this operation using this permission.RequestId:3ebf5395-201e-0023-1ff7-27a758000000
Time:2022-02-22T14:22:00.3240871Z"];
at __randomizedtesting.SeedInfo.seed([203404662522F345:68BCA86A44A7FC4D]:0)
The text was updated successfully, but these errors were encountered: