Add script to dump kubemark master logs

[shyamjvs]

First step towards solving the issue #46109.

cc @kubernetes/test-infra-maintainers @wojtek-t @gmarek

[shyamjvs]

@k8s-bot pull-kubernetes-federation-e2e-gce test this

[shyamjvs]

@k8s-bot kops aws e2e test this
@k8s-bot pull-kubernetes-federation-e2e-gce test this

[shyamjvs]

@k8s-bot pull-kubernetes-federation-e2e-gce test this

[shyamjvs]

@k8s-bot pull-kubernetes-federation-e2e-gce test this

[wojtek-t]

I don't understand the idea behind this script.
Basically, in successful runs, we are somehow gathering all logs from everything we need. Instead of introducing another script, we should ensure that the logic that is running in successful runs is called also in the timed out ones.
@ixdy - I think you worked on it at some point. Feel free to redirect it to someone else.

[shyamjvs]

@wojtek-t Currently the logs for kubemark (similar to real cluster) are collected as part of ginkgo after it finishes running the test suite (see: https://github.com/kubernetes/kubernetes/blob/master/test/e2e/e2e.go#L265). So the logs are 'only' collected after running the e2e tests. Thus if test fails during cluster startup step, we don't get the logs. To counter this problem in the case of real cluster tests, we call DumpClusterLogs in case Up failed (see: https://github.com/kubernetes/test-infra/blob/master/kubetest/e2e.go#L100). I'm replicating the same logic for kubemark too (by PR kubernetes/test-infra#2813). And this script is kind of a wrapper around cluster/log-dump.sh to make it run on the kubemark master (otherwise it'd run on the real master).

[wojtek-t]

OK - this is calling the alerady existing "log-dump.sh" script, I think I missed this initially.
Yeah - that sounds reasonable to me.

[shyamjvs]

@k8s-bot pull-kubernetes-federation-e2e-gce test this

[wojtek-t]

Should this be hardcoded?

[shyamjvs]

Yup. Otherwise it doesn't work. I guess it's because log-dump.sh sets this to config-test.sh (https://github.com/kubernetes/kubernetes/blob/master/cluster/log-dump.sh#L61)

[wojtek-t]

OK - let's see if it will work.

/lgtm
/approve

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: shyamjvs, wojtek-t

Needs approval from an approver in each of these OWNERS Files:

• test/kubemark/OWNERS [shyamjvs,wojtek-t]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[shyamjvs]

@k8s-bot unit test this

[shyamjvs]

@k8s-bot gce etcd3 e2e test this
@k8s-bot kops aws e2e test this

[k8s-ci-robot]

@shyamjvs: The following test(s) failed:

Test name	Commit	Details	Rerun command
pull-kubernetes-federation-e2e-gce	360054a	link	@k8s-bot pull-kubernetes-federation-e2e-gce test this

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[k8s-github-robot]

Automatic merge from submit-queue