Open munishm opened 4 years ago
add to S169
Just to add, this issue with is with azure portal as well, but this happened to me only when the subscription was disabled due to insufficient credit.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @aznetsuppgithub.
I'm in the same boat here. Can't remove resource group because I can't delete a front door app
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @cdnfdsuppgithub.
This exact same thing happens for me whenever one of the front-ends gets stuck in a situation like this, where it says it's still on step 1 of setting up the SSL certificates (at this point, certs that have expired). Can't delete, can't update.
No choice but to create a support ticket and have the team update the status on their end.
This error goes beyond just when you need to delete the front door. I have come into this on many cli front-door commands. Just now, I'm hitting it on configuring rules-engine through the cli. Run one command to create a rules-engine, then try to add action or something and I get "Conflict - The requested operation cannot be executed on the entity as another operation is in progress.". After closing sessions and waiting around 20-30 minutes, the secondary command succeeded. I then hit it again the next command I ran to associate it to a routing-rule. This seems to be a cli client side problem with any of the commands under the az network front-door command group.
The way I believe it "works", Front Door manages tens or even hundreds of traffic entry points around the world. Anytime we make changes, particularly when we make changes that involve SSL configuration, even though the UI (or the CLI, as the case may be) gives you the impression that the work is completed, in reality, it is actually walking around to every single one of those entry points, and updating them with the requested changes... synchronously.
You would think... they would at least do us the kindness of starting to make the updates first in the region we are working in, but best I can tell, the updates start in Bangladesh somewhere and work their way west (a possible unintended side-effect of off-shoring). It's very slow. The more changes or more complicated your Front Door configuration, the longer it takes. A simple cert update took us almost an hour to complete. God help you if you need to fix production quickly.
Same error on a disabled subscription. Can't delete the Front Door.
I feel like frontdoor is still not a "finished" product, there are a number of small issues that seem to affect it, to not saving with no error messages to more complicated such as certificates never provisioning.
I have had a few times now where we have provisioned a DNS entry correctly pointing with a CNAME to the frontdoor and it sits stuck in the domain verification stage forever, i've had to get a microsoft support agent to delete the whole thing so it can be started again - needs to be resolved urgently i'd say.
It doesn't let you delete front door, when trying to delete it in subscription while other resources are allowed to be deleted. Note: This subscription is in disabled state, even though I was able to delete the other resources in subscription other than front-door.
Version Information:
azure-cli 2.2.0 *
command-modules-nspkg 2.0.3 core 2.2.0 * nspkg 3.0.4 telemetry 1.0.4
Extensions: azure-devops 0.17.0 application-insights 0.1.1 front-door 1.0.4
Python location '/opt/az/bin/python3'
Description of issue (in as much detail as possible)
Running the command: az network front-door delete --name --resource-group
output: BadRequest - The requested operation cannot be executed on the entity in the current state.
Debug output: