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

Deleting Azure Network Manager right after deleting ANM Connection resource will ruin the subscription #23188

Open
teowa opened this issue Mar 21, 2023 · 2 comments
Labels
Network Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@teowa
Copy link
Contributor

teowa commented Mar 21, 2023

Swagger:

Reproduce Step:

  1. Create the NetworkManager and ScopeConnection or SubscriptionNetworkManagerConnections or ManagementGroupNetworkManagerConnections resource.
  2. Call the ScopeConnections_Delete, SubscriptionNetworkManagerConnections_Delete or NetworkManagers_Delete, and then immediately (within one sec) calling the NetworkManagers_Delete method.
  3. Cannot create new Network Manager same in test subscription any more. Creating a new Network Manager using the same subscription as scope will fail and returns error like: "Cannot have two Network Managers applied to the same object overlapping scope accesses. Scope id: /subscriptions/xxx. Network Manager Id: /subscriptions/xxx/resourceGroups/wt-media-resources/providers/Microsoft.Network/networkManagers/wtest. Overlapping accesses: SecurityAdmin", but step2 has successfully deleted the ANM, and there should be no ANM covering the subscription.
@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Mar 21, 2023
@teowa teowa changed the title Deleting Azure Network Manager right after deleting ANM Connection resource will break the subscription used as ANM scope Deleting Azure Network Manager right after deleting ANM Connection resource will ruin the subscription Mar 21, 2023
teowa added a commit to teowa/terraform-provider-azurerm that referenced this issue Mar 21, 2023
@JackTn JackTn added Network Service Attention Workflow: This issue is responsible by Azure service team. labels Mar 21, 2023
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Mar 21, 2023
@ghost
Copy link

ghost commented Mar 21, 2023

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

Issue Details

Swagger:

Reproduce Step:

  1. Create the NetworkManager and ScopeConnection or SubscriptionNetworkManagerConnections or ManagementGroupNetworkManagerConnections resource.
  2. Call the ScopeConnections_Delete, SubscriptionNetworkManagerConnections_Delete or NetworkManagers_Delete, and then immediately (within one sec) calling the NetworkManagers_Delete method.
  3. Cannot create new Network Manager same in test subscription any more. Creating a new Network Manager using the same subscription as scope will fail and returns error like: "Cannot have two Network Managers applied to the same object overlapping scope accesses. Scope id: /subscriptions/xxx. Network Manager Id: /subscriptions/xxx/resourceGroups/wt-media-resources/providers/Microsoft.Network/networkManagers/wtest. Overlapping accesses: SecurityAdmin", but step2 has successfully deleted the ANM, and there should be no ANM covering the subscription.
Author: teowa
Assignees: -
Labels:

Network, Service Attention, needs-triage

Milestone: -

@tombuildsstuff
Copy link
Contributor

ping @aznetsuppgithub any update here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Network Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants