Segfault when running pilot discovery with multiple registries #186
Description
Is this a BUG or FEATURE REQUEST?:
BUG
Did you review istio.io/help and existing issues to identify if this is already solved or being worked on?:
YES
Bug:
Y
What Version of Istio and Kubernetes are you using, where did you get Istio from, Installation details
istioctl version
Version: 0.5.0
GitRevision: c9debceacb63a14a9ae24df433e2ec3ce1f16fc7
User: root@211b132eb7f1
Hub: docker.io/istio
GolangVersion: go1.9
BuildStatus: Clean
kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.2", GitCommit:"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b", GitTreeState:"clean", BuildDate:"2018-01-18T10:09:24Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.6", GitCommit:"6260bb08c46c31eea6cb538b34a9ceb3e406689c", GitTreeState:"clean", BuildDate:"2017-12-21T06:23:29Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Is Istio Auth enabled or not ?
Auth Disabled
What happened:
I'm attempting to run pilot (0.5.0) using both Consul and Kubernetes as service registries. Either one works alone, but when they are both configured pilot/pkg/serviceregistry/aggregate/controller.go segfaults.
Here are the parameters I used for pilot discovery
discovery
Image:
docker.io/istio/pilot:0.5.0
Environment variables:
POD_NAME: istio-pilot-67dd8dbdd4-vpn5q
POD_NAMESPACE: istio-system
Commands:
-
Args:
discovery
-v
2
--registries
Consul, Kubernetes
--consulserverURL
http://consul.dev.cloud.internal.eero:8500
--admission-service
istio-pilot
What you expected to happen:
pilot not to crash
How to reproduce it:
Run pilot discovery with included parameters.
Full stacktrace attached
logs-from-discovery-in-istio-pilot.txt