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

e2e: pass namespace when calling kubectl stop #8303

Closed
wants to merge 1 commit into from

Conversation

ixdy
Copy link
Member

@ixdy ixdy commented May 15, 2015

After #7544, resources in the kubectl e2e test were being created in their own namespaces, but due to a bug introduced by #6194, kubectl stop was not failing, even though these resources did not exist in the default namespace, since the error was being ignored. This was not apparent until #8249 was merged, at which point it caused the kubectl stop calls in cleanup to fail.

This is now resolved by passing the namespace to kubectl in most of the test cases; in one case, I just removed the cleanup call entirely, as (I think) it's expected that one of the resources shouldn't exist, but I wasn't sure how best to handle that. Cleanup should still be handled adequately by the namespace being deleted, anyway.

Fixes #8300.

@ixdy
Copy link
Member Author

ixdy commented May 15, 2015

This still suggests that at some point before #6194 kubectl stop did not error when resources didn't exist, but now it does. I'm not sure if this change in behavior was intentional?

@piosz piosz self-assigned this May 15, 2015
@piosz
Copy link
Member

piosz commented May 15, 2015

Duplicate of #8309

@piosz piosz closed this May 15, 2015
@ixdy ixdy mentioned this pull request May 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

kubectl e2e tests broken
3 participants