istio: istio-mixer-post-install first run fails

When installing Istio using helm the istio-mixer-post-install job is being triggered but the first try fails:

istio-mixer-post-install-dcfxt              0/1       Error       0          2m
istio-mixer-post-install-drlr7              0/1       Completed   0          1m

The log from the failed run says that it got timeout:

2018-06-21 16:01:16.371423 I | proto: duplicate proto type registered: google.protobuf.Any
2018-06-21 16:01:16.371646 I | proto: duplicate proto type registered: google.protobuf.Duration
2018-06-21 16:01:16.371869 I | proto: duplicate proto type registered: google.protobuf.Timestamp
attributemanifest "kubernetes" created
stdio "handler" created
logentry "accesslog" created
rule "stdio" created
metric "requestcount" created
metric "requestduration" created
metric "requestsize" created
metric "responsesize" created
metric "tcpbytesent" created
metric "tcpbytereceived" created
prometheus "handler" created
rule "promhttp" created
rule "promtcp" created
kubernetesenv "handler" created
rule "kubeattrgenrulerule" created
rule "tcpkubeattrgenrulerule" created
kubernetes "attributes" created
destinationrule "istio-policy" created
destinationrule "istio-telemetry" created
Error from server (Timeout): error when creating "/tmp/mixer/custom-resources.yaml": Timeout: request did not complete within allowed duration

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 5
Comments: 20 (16 by maintainers)

Most upvoted comments

This is coming up for me in an EKS cluster using 1.0

thedevelopnik on Aug 14, 2018

We need to figure a way to have dependencies between the helm charts as galley needs to available before starting the other charts

https://github.com/istio/istio/pull/6648 adds an explicit dependency check between the custom-resource jobs and galley.

ayj on Jun 27, 2018

@ymesika I’ll ask the TOC mailer for a commitment so we aren’t left guessing and get back to you.

Cheers -steve

sdake on Jun 26, 2018