You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2018-11-08T15:36:56.3485999Z + azure:msi:UserAssignedIdentity msi-app creating
2018-11-08T15:36:57.8096273Z + azure:msi:UserAssignedIdentity msi-app created
2018-11-08T15:36:58.0442362Z + azure:role:Assignment app-kv-role creating
2018-11-08T15:37:00.1007517Z + azure:role:Assignment app-kv-role creating error: Plan apply failed: authorization.RoleAssignmentsClient#Create: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="PrincipalNotFound" Message="Principal 12bd9f9c9c1541b8a727c892ed19e1f2 does not exist in the directory ***."
2018-11-08T15:37:00.1014845Z + azure:role:Assignment app-kv-role **creating failed** error: Plan apply failed: authorization.RoleAssignmentsClient#Create: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="PrincipalNotFound" Message="Principal 12bd9f9c9c1541b8a727c892ed19e1f2 does not exist in the directory ***."
The text was updated successfully, but these errors were encountered:
mpp-oliverh
changed the title
Strange race condition with new UserAssignedIdentity() and new
Race condition with msi.UserAssignedIdentity and role.Assignment
Nov 8, 2018
If I create a new UserAssignedIdentity then immediately try to assign it a role it complains that the principalId doesn't exist in the directory.
I assume this is a bug / peculiarity with Azure itself because the dependency chain looks fine... is there a way of working around this?
Thanks,
The text was updated successfully, but these errors were encountered: