Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Testing] Describe unhealthy pods when tests clean up. #2554

Merged
merged 2 commits into from
Nov 6, 2019

Conversation

Bobgy
Copy link
Contributor

@Bobgy Bobgy commented Nov 6, 2019

For debugging postsubmit test failure: pod with image pull back off.

Related reference:

However, I don't want to workaround kubectl limitations. This one is good enough. We can improve when we actually see crash loop back off issue.

/assign @jingzhang36
/area testing


This change is Reviewable

@Bobgy Bobgy changed the title [Testing] Describe unhealthy pods after failure. [Testing] Describe unhealthy pods when tests clean up. Nov 6, 2019
@Bobgy
Copy link
Contributor Author

Bobgy commented Nov 6, 2019

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Bobgy

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jingzhang36
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot merged commit 202e748 into kubeflow:master Nov 6, 2019
@Bobgy Bobgy deleted the describe_pods_on_failure branch November 6, 2019 08:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants