-
Notifications
You must be signed in to change notification settings - Fork 114
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
functest: add retry for rdma functionel test #817
functest: add retry for rdma functionel test #817
Conversation
Thanks for your PR,
To skip the vendors CIs, Maintainers can use one of:
|
704d7ec
to
f68bdf1
Compare
Pull Request Test Coverage Report for Build 12373006144Details
💛 - Coveralls |
output, _, err = runCommandOnConfigDaemon(testNode, "/bin/bash", "-c", "cat /host/proc/cmdline | grep ib_core.netns_mode=0 | wc -l") | ||
Expect(err).ToNot(HaveOccurred()) | ||
Expect(strings.HasPrefix(output, "0")).To(BeTrue()) | ||
Expect(strings.HasPrefix(output, "0")).To(BeTrue(), fmt.Sprintf("kernel args are not right, printing current kernel args %s", cmdlineOutput)) | ||
|
||
output, _, err = runCommandOnConfigDaemon(testNode, "/bin/bash", "-c", "cat /host/proc/cmdline | grep ib_core.netns_mode=1 | wc -l") | ||
Expect(err).ToNot(HaveOccurred()) | ||
Expect(strings.HasPrefix(output, "1")).To(BeTrue()) | ||
Expect(strings.HasPrefix(output, "1")).To(BeTrue(), fmt.Sprintf("kernel args are not right, printing current kernel args %s", cmdlineOutput)) |
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.
can we refactor this to?
Expect(cmdlineOutput).To(ContainSubstring("ib_core.netns_mode=1"))
Expect(cmdlineOutput).ToNot(ContainSubstring("ib_core.netns_mode=0"))
The same for the other /host/proc/cmdline
asssertion
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.
you are right less execs!
this is needed because after a reboot on a single node the operator webhook may not be ready Signed-off-by: Sebastian Sch <[email protected]>
f68bdf1
to
0c4edb3
Compare
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.
LGTM!
this is needed because after a reboot on a single node the operator webhook may not be ready