[log exporter] detect-node-names: command not found

[nareddyt]

What happened: When running our OSS Prow jobs based on the kubekins-e2e image, our jobs fail with the following error:

./cluster/log-dump/log-dump.sh: line 697: detect-node-names: command not found

This failure happens during kubekins cluster cleanup. The actual script we provide finishes successfully, just cleanup defined by kubekins fails.

What you expected to happen:

Cleanup is successful. Either logs are exported or (as a workaround) log exporter is disabled.

How to reproduce it (as minimally and precisely as possible): /retest any open PR in https://github.com/GoogleCloudPlatform/esp-v2. 5 or so jobs fail with this error during cleanup

Please provide links to example occurrences, if any:

See the end of the logs in this job run: https://oss.gprow.dev/view/gs/oss-prow/pr-logs/pull/GoogleCloudPlatform_esp-v2/705/ESPv2-gke-e2e-http-bookstore-managed/1536405146936807424

Anything else we need to know?:

Prow job configuration:

https://github.com/GoogleCloudPlatform/oss-test-infra/blob/3879dcc38c59d3cba9daf72f30f8f76e54d8cf04/prow/prowjobs/GoogleCloudPlatform/esp-v2/esp-v2.yaml#L153-L211

Notice it is using image gcr.io/k8s-testimages/kubekins-e2e:latest-1.21, which is the latest k8s stable version offered by GKE today.

[nareddyt]

/sig testing

[nareddyt]

Friendly ping, this issue is still occuring

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR 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 and PRs.

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages 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:

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

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

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

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.