Skip to content
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

az identity federated-credential delete doesn't work when UAMI has delete lock #28242

Open
Vegoo89 opened this issue Jan 24, 2024 · 3 comments
Open
Assignees
Labels
Auto-Assign Auto assign by bot Auto-Resolve Auto resolve by bot customer-reported Issues that are reported by GitHub users external to the Azure organization. Managed Identity For `az identity` only question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.
Milestone

Comments

@Vegoo89
Copy link

Vegoo89 commented Jan 24, 2024

Describe the bug

Seems like federated identity delete lock is inherited from UAMI to Federated Credentials and because of that command fails with (ScopedLocked) error

Related command

az identity federated-credential delete --identity-name <uami_name> --name <identity_name> -g <uami_rg> --yes

Errors

(ScopeLocked) The scope '<identity_id>' cannot perform delete operation because following scope(s) are locked: '<uami_id>'. Please remove the lock and try again.

Issue script & Debug output

Since I can't copy it from work I can just tell that debug doesn't provide any additional, useful insight for resolving this issue

Expected behavior

UAMI delete lock is not inherited to Federated Credential and Federated Credential is removed.

Environment Summary

azure-cli 2.48.1

core 2.48.1
telemetry 1.0.8

Extensions:
aks-preview 0.5.137
quota 0.1.0

Dependencies:
msal 1.20.0
azure-mgmt-resource 22.0.0

Additional context

No response

@Vegoo89 Vegoo89 added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Jan 24, 2024
Copy link

Hi @Vegoo89,

2.48.1 is not the latest Azure CLI(2.56.0).

If you haven't already attempted to do so, please upgrade to the latest Azure CLI version by following https://learn.microsoft.com/en-us/cli/azure/update-azure-cli.

@azure-client-tools-bot-prd azure-client-tools-bot-prd bot added the Auto-Resolve Auto resolve by bot label Jan 24, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. Auto-Assign Auto assign by bot Managed Identity For `az identity` only labels Jan 24, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added Azure CLI Team The command of the issue is owned by Azure CLI team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jan 24, 2024
@yonzhan
Copy link
Collaborator

yonzhan commented Jan 24, 2024

Thank you for opening this issue, we will look into it.

@yonzhan yonzhan added this to the Backlog milestone Jan 24, 2024
@yonzhan yonzhan removed the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Jan 24, 2024
@zhoxing-ms zhoxing-ms added the Service Attention This issue is responsible by Azure service team. label Jan 24, 2024
Copy link
Contributor

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @varunkch.

@yonzhan yonzhan removed the Azure CLI Team The command of the issue is owned by Azure CLI team label Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot Auto-Resolve Auto resolve by bot customer-reported Issues that are reported by GitHub users external to the Azure organization. Managed Identity For `az identity` only question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants