CODEWITHSUNDEEP
azureazure-redis-cache
Micah Zoltu
Micah Zoltu

Reputation: 7432

"There are no locations available." when trying to create an Azure Redis Cache

When I try to create a new Azure Redis Cache and choose a location I just get a "There are no locations available." message.1 Setting everything else first still results in the same error. Refreshing the page doesn't resolve the issue. The problem occurs in both IE and Chrome.

error

Upvotes: 0

Views: 188

Answers (2)

Micah Zoltu
Micah Zoltu

Reputation: 7432

After working with the Azure team via email we were able to narrow down the problem and find a workaround.

There are 3 problems at work here that result in my symptoms:

  1. The various New blades in the portal will default you to a disabled subscription. I believe they currently default to the first subscription (oldest) which may not be an active subscription. This results in the default behavior upon choosing a blade to be that of no-subscription.

  2. The New Redis Cache blade will only show locations if you have selected a valid (not disabled) subscription. This behavior differs from the other New blades (such as Create VM) which will show you locations even if you have a disabled subscription selected.

  3. Changing the resource group will automatically change the subscription and lock it, but changing the subscription in this way will not trigger an update to the blade. This means that the locations don't get updated for the new subscription because the subscription-changed-event (made up name) was not fired. In my case, I was always changing the subscription by way of changing the resource group, so I was never able to set the location.

The workaround:

Simply change to an active subscription before choosing a resource group. This will cause the locations list to be updated, and you can then choose a resource group after.

Upvotes: 1

Mike Harder
Mike Harder

Reputation: 1865

Thanks for reporting this. It seems to be a bug in the portal. I can reproduce it if I click "Location" immediately after the "New Redis Cache" blade opens. However, if I wait a few seconds before clicking "Location", it doesn't repro.

As a workaround, if you close and reopen the "Location" blade it should populate correctly.

We will also work on fixing this in the portal.

Finally, for any issues with Azure Redis Cache you can contact us via email at [email protected].

Upvotes: 1

Related Questions