No region is populated for Azure accounts

[Mozanrath]

Just for reference I used the Azure quickstart template to do an initial Spinnaker installation. Also, the cloud provider was an Azure account (for Azure VM scale sets, not a Kubernetes cluster).

I added an account (Azure) following the account setup documentation. However, when I go to create a new security group or load balancer, no region is found. I should be able to select the same region as the associated Resource group.

The azure account was added with no errors (even checked logs, clouddriver, echo, etc.). Since there is no region found, this essentially blocks adding any of these objects.

Screenshot: https://imgur.com/hyQmzdM

[joaosamuelp]

Same problem.

[Mozanrath]

Just fyi, I've tried running on different spinnaker version, 1.4.2 / 1.5.2 as well as on instances that were created from Azure quickstart templates, and from scratch.
In all cases, I eventually run in to the same blocking issue.

[torumakabe]

I have encountered the same issue.

[kranthiB]

Even I experience the same with versions - 1.3.x / 1.4.x / 1.5.x. But, it got success when I set to 1.0.0 version.

[hafizullah]

I am having exactly the same problem!!! is there any update on this bug please?

[durgeshworks]

I am also facing same issue. Can somebody help me.

[cmketchu]

I am also having the same issue on v1.7.3. Any updates on this bug? Was anyone able to resolve it?

[gclabon]

Seeing this on 1.8.0 and 1.8.1, is there any known way to resolve this?

[cmketchu]

@gclabon We did eventually figure out why no region was populated. We had configured Spinnaker for Azure with Halyard. Halyard was lacking a property to set the region when adding Azure. We were able to work around this by using a custom configuration for the cloud driver and setting regions: ["eastus"] on the azure config. That populated the drop down and we were able to continue with creation of security groups and load balancers.

[hafizullah]

Hi @cmketchu that is fantastic news, could you please give us an idea as to which file you have modified?

[cmketchu]

@hafizullah Basically you need to setup a custom configuration for the could driver. We followed the directions that spinnaker documents here.

https://www.spinnaker.io/reference/halyard/custom/

First we ran hal deploy apply after adding the azure provider. Then we copied /opt/spinnaker/config/clouddriver.yml (generated by hal deploy apply on the spinnaker machine or pod) into ~/.hal/default/profiles and added regions under azure in the following format: regions: ["eastus"]. Then running hal deploy apply again uses the custom configuration.

Its easy to forget you have a custom configuration in place so be aware that config updates to halyard in the future won't change the cloud driver configuration with the custom config in place. We copied the whole file, but you may be able to find a way to override only a portion.

[gclabon]

Thats great, thanks @cmketchu

[contacttapan]

cmketchu solution . works!!!
Thanks

[spinnakerbot]

This issue is tagged as 'stale' and hasn't been updated in 45 days, so we are tagging it as 'to-be-closed'. It will be closed in 45 days unless updates are made. If you want to remove this label, comment:

@spinnakerbot remove-label to-be-closed

[spinnakerbot]

This issue is tagged as 'to-be-closed' and hasn't been updated in 45 days, so we are closing it. You can always reopen this issue if needed.

[subhashchand]

Also having same problem with latest version 1.9.5 (Bright).