Unable to see logs from /log endpoint when pod is cleaned up

[mohitsharma-in]

What would you like to be added: This will help in providing better user experience from deck in order to check logs

Why is this needed: When the pods are being cleaned up after completion, logs are not visible rather is shows Log not found: pods "fe5f2481-2f30-11ed-a59e-fe72ba29f753" not found Example: https://prow.k8s.io/log?job=ci-test-infra-prow-checkconfig&id=1567735727028965376

Logs are available on GCS https://storage.googleapis.com/kubernetes-jenkins/logs/ci-test-infra-prow-checkconfig/1567735727028965376/build-log.txt

Idea is to show logs on /log endpoint irrespective of pod is available or cleaned up

[mohitsharma-in]

/sig testing

[jbpratt]

/area prow prow/deck

[jbpratt]

Some additional information:

The /log handler is configured here https://github.com/kubernetes/test-infra/blob/c2d8edcd1586aa11409dd167a5b2fd11bfc711e6/prow/cmd/deck/main.go#L448 which fetches job logs here https://github.com/kubernetes/test-infra/blob/c2d8edcd1586aa11409dd167a5b2fd11bfc711e6/prow/cmd/deck/main.go#L1380 then grabbing the pod logs here https://github.com/kubernetes/test-infra/blob/c2d8edcd1586aa11409dd167a5b2fd11bfc711e6/prow/deck/jobs/jobs.go#L250

[mohitsharma-in]

@jbpratt Can you help me how it's done differently on lens

[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.

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

[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.