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

deploy.sh fails because it does not generate globally unique names for azure services #45

Open
asaikali opened this issue Aug 11, 2022 · 0 comments

Comments

@asaikali
Copy link
Collaborator

asaikali commented Aug 11, 2022

Some azure services require globally unique names across all of azure according to azure docs Naming rules and restrictions for Azure resources the Redis and postgres services must have globally unique names.

The ./azure/deploy.sh fails when it tries to create the redis cache because the name is not globally unique.

./deploy.sh -g demo -r germanywestcentral -s demo-asa-instance
Configure azure defaults resource group: demo and spring demo-asa-instance
Creating Azure Cache for Redis Instance fitness-cache in location eastus
(NameNotAvailable) An error occured when trying to reserve the DNS name for the cache instance. This may be a temporary issue if a cache instance of this name was recently deleted. Please choose a different name or try again later.
RequestID=ec628194-f0cb-47b5-b745-e26da796ee9d
Code: NameNotAvailable
Message: An error occured when trying to reserve the DNS name for the cache instance. This may be a temporary issue if a cache instance of this name was recently deleted. Please choose a different name or try again later.
RequestID=ec628194-f0cb-47b5-b745-e26da796ee9d

It seems that the azure redis service requires a unique dns name for each instance of redis under the .redis.cache.windows.net domain. The script should be modified to generate a unique name for the redis service.

Also the postgres service creation will fail with the same issue.

@asaikali asaikali changed the title deploy.sh script can't create redis instance deploy.sh fails because it does not generate globally unique names for azure services Aug 11, 2022
asaikali added a commit that referenced this issue Jul 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant