Azure: consul cluster start fails during auto discovery #3875
Labels
type/bug
Feature does not function as expected
type/crash
The issue description contains a golang panic and stack trace
Milestone
Description of the Issue (and unexpected/desired result)
Trying to start up consul server agent that is configured to use the azure provider for the rejoin.
The process exits with
panic: runtime error: invalid memory address or nil pointer dereference
.I saw an old bug report #3193 that has the same kind of exception. But in that stacktrace it seems to come from
consul/command/agent.(*Config).discoverAzureHosts
and my exception comes fromhashicorp/go-discover/provider/azure.fetchAddrsWithTags
.Reproduction steps
Config file:
I start it up with
consul.exe agent -config-dir "c:\consul\consul.d" -log-level trace
And then I get
consul version
for both Client and ServerServer:
Consul v1.0.5
consul info
for both Client and ServerClient:
Operating system and Environment details
Windows server 2016 datacenter on azure
I hope this rings a bell somewhere. If I can help in providing more info or testing something i'd be happy to do so.
kind regards,
Arno den Uijl
The text was updated successfully, but these errors were encountered: