[KeyVault] test failing in nightly runs

[v-yilinhu]

KeyVault nightly test runs are failing with:

Error Message
Azure.RequestFailedException : The role assignment already exists. (Activity ID: 24ef1f64-c777-11eb-8675-000d3af54d67)
Status: 400 (Bad Request)
ErrorCode: RoleAssignmentExists

Content:
{"error":{"code":"RoleAssignmentExists","message":"The role assignment already exists. (Activity ID: 24ef1f64-c777-11eb-8675-000d3af54d67)"}}

Headers:
x-ms-server-latency: REDACTED
Cache-Control: no-cache
X-Content-Type-Options: REDACTED
x-ms-request-id: 24ef1f64-c777-11eb-8675-000d3af54d67
Strict-Transport-Security: REDACTED
Content-Security-Policy: REDACTED
X-Frame-Options: REDACTED
Content-Type: application/json; charset=utf-8
Content-Length: 141

Stack Trace
at Azure.Security.KeyVault.Administration.RoleAssignmentsRestClient.CreateAsync(String vaultBaseUrl, String scope, String roleAssignmentName, RoleAssignmentCreateParameters parameters, CancellationToken cancellationToken) in /_/sdk/keyvault/Azure.Security.KeyVault.Administration/src/Generated/RoleAssignmentsRestClient.cs:line 192
at Azure.Security.KeyVault.Administration.KeyVaultAccessControlClient.CreateRoleAssignmentAsync(KeyVaultRoleScope roleScope, String roleDefinitionId, String principalId, Nullable1 roleAssignmentName, CancellationToken cancellationToken) in /_/sdk/keyvault/Azure.Security.KeyVault.Administration/src/KeyVaultAccessControlClient.cs:line 466 at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.<>c__DisplayClass4_01.<g__Await|0>d.MoveNext() in /mnt/vss/_work/1/s/sdk/core/Azure.Core.TestFramework/src/Instrumentation/DiagnosticScopeValidatingInterceptor.cs:line 91
--- End of stack trace from previous location where exception was thrown ---
at System.Threading.Tasks.ValueTask1.get_Result() at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.<>c__DisplayClass5_01.<b__0>d.MoveNext() in /mnt/vss/_work/1/s/sdk/core/Azure.Core.TestFramework/src/Instrumentation/DiagnosticScopeValidatingInterceptor.cs:line 142
--- End of stack trace from previous location where exception was thrown ---
at System.Threading.Tasks.ValueTask1.get_Result() at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.ValidateDiagnosticScope[T](Func1 action, MethodInfo methodInfo, String source) in /mnt/vss/_work/1/s/sdk/core/Azure.Core.TestFramework/src/Instrumentation/DiagnosticScopeValidatingInterceptor.cs:line 165
at Azure.Security.KeyVault.Administration.Tests.AccessControlClientLiveTests.GetRoleAssignment() in /mnt/vss/_work/1/s/sdk/keyvault/Azure.Security.KeyVault.Administration/tests/AccessControlClientLiveTests.cs:line 164
at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter1.BlockUntilCompleted() at NUnit.Framework.Internal.MessagePumpStrategy.NoMessagePumpStrategy.WaitForCompletion(AwaitAdapter awaiter) at NUnit.Framework.Internal.AsyncToSyncAdapter.Await(Func1 invoke)
at NUnit.Framework.Internal.Commands.TestMethodCommand.RunTestMethod(TestExecutionContext context)
at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context)
at NUnit.Framework.Internal.Commands.BeforeAndAfterTestCommand.<>c__DisplayClass1_0.b__0()
at NUnit.Framework.Internal.Commands.BeforeAndAfterTestCommand.RunTestMethodInThreadAbortSafeZone(TestExecutionContext context, Action action)

For more details check here:

• https://dev.azure.com/azure-sdk/internal/_build/results?buildId=929797&view=results

[heaths]

Thank you for monitoring these, but please note I do monitor the test runs and mitigate as needed. Please do not open separate issues. The current set of issues has to do with potential service issues and have a single cause/mitigation. I have an internal thread with the service team.