Deployment name conflict

[danmelamed]

dmdp2 failed with

Unable to edit or replace deployment 'Management_Center': previous deployment from '7/6/2016 8:21:16 PM' is still active (expiration time is '7/13/2016 8:21:15 PM'). Please see https://aka.ms/arm-deploy for usage details. (Code: DeploymentActive)

This is odd in several ways:

• There are no errors in the audit log.
• The timestamp is in the future
• I'm certain that there is no such RG at the moment.
• The name of the deployment seems too generic -- 'Management_Center'. Do we not add unique IDs to deployment names?
• The RG thinks the deployment was successful. I can see the MC in my browser, but when I try to log in I get a runtime error.

[lhoang29]

Ah I had some pending changes to fix this but it made the template unreadable. I'm checking if it's possible to use timestamp...

[sidsen]

Louie, can you clarify your statement above? Are you saying this was caused by some temporary changes you made that have since been fixed? (I don't really understand the issue here, it seems like an ARM error message?)

[lhoang29]

I was about to make the deployment names unique but that required using too many macros that made the template unreadable. Gonna see if there's a better way to do it.

[sidsen]

But we've used the same names in multiple deployments in the past without trouble... seems like something else went wrong with Dan's deployment?

[lhoang29]

probably multiple deployments going on at the same time.

[lhoang29]

@sidsen, @danmelamed are you guys ok with moving this to post R0 milestone? I can fix it but the template will look rather unreadable since every deployment name is going to contain macros in it (for uniqueness). Concurrent deployments will probably not happen that often for our users either.

[danmelamed]

Yes :)