-
Notifications
You must be signed in to change notification settings - Fork 24
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: bridge CNI setup fixes for Fedora/containerd. #361
Conversation
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.
I had an issue with a regexp with '(#CNI_NETWORK#)', but it worked fine with only 'CNI_NETWORK'. Would the latter work for you?
af298ad
to
3d12a01
Compare
Thanks for spotting that ! My tree was not up-to-date, missing your regexp pattern fix commit (plus instead of moving that block earlier it was accidentally copying it). So it recreated the other bug you just fixed and it wouldn't have worked at all. Let me put up an e2e test run to double-check that this committed and pushed version works... |
Okay, it looks good. Spun up the VM and the cluster and successfully ran all tests. |
Signed-off-by: Krisztian Litkey <krisztian.litkey@intel.com>
When using the bridge plugin, configure it earlier, right after the basic runtime configuration has been created, before NRI is enabled or the runtime restarted. This should make it sure that the node does not linger in a NotReady state causing false test failures. Signed-off-by: Krisztian Litkey <krisztian.litkey@intel.com>
3d12a01
to
e2b4e2b
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
Fix e2e tests runnning with bridge CNI plugin on fedora. In particular,
These fixes should ensure that the node does not stay lingering in NotReady state, causing false test failures/positives.