I just tried to install 1.1-snapshot.5 into OpenShift 3.11 and I’m getting errors. Hoping someone can see what I’m doing wrong.
I run this command:
helm init --client-only
helm repo add istio.io https://storage.googleapis.com/istio-prerelease/daily-build/master-latest-daily/charts
helm dep update /istio-1.1-snapshot.5/install/kubernetes/helm/istio
helm template "/istio-1.1-snapshot.5/install/kubernetes/helm/istio" --name istio --namespace istio-system > /tmp/istio.yaml
helm apply -f /tmp/istio.yaml
and I get this at the end:
unable to recognize "/tmp/istio.yaml": no matches for kind "attributemanifest" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "attributemanifest" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "handler" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "logentry" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "logentry" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "rule" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "rule" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "metric" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "metric" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "metric" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "metric" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "metric" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "metric" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "metric" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "metric" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "handler" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "rule" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "rule" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "rule" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "rule" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "handler" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "rule" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "rule" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "kubernetes" in version "config.istio.io/v1alpha2"
unable to recognize "/tmp/istio.yaml": no matches for kind "DestinationRule" in version "networking.istio.io/v1alpha3"
unable to recognize "/tmp/istio.yaml": no matches for kind "DestinationRule" in version "networking.istio.io/v1alpha3"
I tried running the helm install several times but I still get those errors.
I now have several pods that can’t come up:
$ oc get pods -n istio-system
NAME READY STATUS RESTARTS AGE
istio-citadel-644bfb5c47-hmwm7 1/1 Running 0 14m
istio-cleanup-secrets-1.1.0-snapshot.5-kk5mk 0/1 Completed 0 14m
istio-egressgateway-769bcc9cd-fvxnn 1/1 Running 0 14m
istio-galley-dbc767799-5468k 0/1 CrashLoopBackOff 7 14m
istio-ingressgateway-59f98db585-ggshc 1/1 Running 0 14m
istio-pilot-5bcbc558c-vwd4s 1/2 Running 0 14m
istio-policy-64cfb8798b-pm8xp 1/2 CrashLoopBackOff 9 14m
istio-sidecar-injector-ff98d6cff-ffm46 1/1 Running 0 14m
istio-telemetry-5966b85884-h6b5g 1/2 CrashLoopBackOff 9 14m
prometheus-c4b6997b-fvqzm 1/1 Running 0 14m
Galley is seg-faulting:
|2019-01-30T19:54:07.155376Z info Istio Galley: root@79518220-20ee-11e9-86e9-0a580a2c0304-docker.io/istio-1.1.0-snapshot.5-f1eab0a25dd6f37be03951698be0e84b120ec18f-dirty-Modified|
||Starting gRPC server on tcp://0.0.0.0:9901|
||panic: runtime error: invalid memory address or nil pointer dereference|
||[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1a65552]|
||goroutine 98 [running]:|
||istio.io/istio/galley/pkg/server.(*Server).Run(0x0)|
||/workspace/go/src/istio.io/istio/galley/pkg/server/server.go:217 +0x22|
||istio.io/istio/galley/pkg/server.RunServer(0xc4200f20c0, 0x21e0cc0, 0xc4205c8c80, 0x21e0cc0, 0xc4205c8cd0)|
||/workspace/go/src/istio.io/istio/galley/pkg/server/server.go:277 +0x1b3|
||created by istio.io/istio/galley/cmd/galley/cmd.GetRootCmd.func2|
||/workspace/go/src/istio.io/istio/galley/cmd/galley/cmd/root.go:88 +0x3c8|
l see no obvious errors in telemetry or policy logs. Telemetry pod AND policy pod both have this identical event re-occuring:
Killing container with id docker://mixer:Container failed liveness probe.. Container will be killed and recreated.
UPDATE: I tried adding this repo (helm repo add), but still basically the same problems: “https://storage.googleapis.com/istio-release/releases/1.1.0-snapshot.5/charts”