Logs are obtained after the cluster is up and before the tests run

[aojea]

As a consequence there is no possibility of debugging test failures, IIRC the logs should be obtained before we are tearing down the cluster, but when this option was added , it got added to the Up() hook https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-gce-conformance-latest-kubetest2/1845682784069226496

fb21a08

It seems the AWS one logs correctly

https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-cloud-provider-aws-e2e-kubetest2/1845768599910748160

[aojea]

/cc @BenTheElder @krzyzacy

[aojea]

Suggestions from @soltysh seems the best one, moving the dump of the logs to the Down() hook

https://github.com/kubernetes-sigs/kubetest2/blob/master/kubetest2-gce/deployer/down.go#L28

[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