[failing job] ci-kubernetes-e2e-gce-network-metric-measurement

[aojea]

The jobs is permanent failing https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gce-network-metric-measurement/1993709404502888448 but I can't say since when

there are yaml manifest errors

I1126 16:09:26.458286   15138 framework.go:276] Applying templates for "manifests/networktestrequests.yaml"
I1126 16:09:26.458307   15138 framework.go:287] Applying manifests/networktestrequests.yaml
E1126 16:09:26.458588   15138 network_performance_measurement.go:338] TemplateToObject error: replacing placeholders error: Invalid YAML Template
I1126 16:09:26.458597   15138 framework.go:276] Applying templates for "manifests/networktestrequests.yaml"
I1126 16:09:26.458603   15138 framework.go:287] Applying manifests/networktestrequests.yaml
E1126 16:09:26.458898   15138 network_performance_measurement.go:338] TemplateToObject error: replacing placeholders error: Invalid YAML Template
I1126 16:09:26.458906   15138 framework.go:276] Applying templates for "manifests/networktes

Not many changes on those manifests https://github.com/kubernetes/perf-tests/commits/master/clusterloader2/pkg/measurement/common/network

It does not seem the config has changed much, this was last change kubernetes/test-infra@3939472

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten