-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Add the existence check of /proc/net/nf_conntrack #69589
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -77,6 +77,16 @@ var _ = SIGDescribe("Network", func() { | |
|
||
zero := int64(0) | ||
|
||
// Some distributions (Ubuntu 16.04 etc.) don't support the proc file. | ||
_, err := framework.IssueSSHCommandWithResult( | ||
"ls /proc/net/nf_conntrack", | ||
framework.TestContext.Provider, | ||
clientNodeInfo.node) | ||
if err != nil && strings.Contains(err.Error(), "No such file or directory") { | ||
framework.Skipf("The node %s does not support /proc/net/nf_conntrack", clientNodeInfo.name) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is there no other way to accomplish what this test is trying to do? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, that is ideal. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. necro-ing a bit but ... it looks to me like you're expected to use see e.g. netdata/netdata#161 (comment) cc @aojea There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. interesting, thanks for the pointer, it also mentions
that I'd say is the cause of the flakiness in the TCP_CLOSE_WAIT test I'll submit a new PR to change this There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
} | ||
framework.ExpectNoError(err) | ||
|
||
clientPodSpec := &v1.Pod{ | ||
ObjectMeta: metav1.ObjectMeta{ | ||
Name: "e2e-net-client", | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just add
(exit code %d, stderr %v)
would work.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice idea, thanks.
I will update this.