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
Bug 1939605: cri-o+kuryr: Switch to proper netns management … #12316
Bug 1939605: cri-o+kuryr: Switch to proper netns management … #12316
Conversation
@dulek: No Bugzilla bug is referenced in the title of this pull request. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@dulek: This pull request references Bugzilla bug 1939605, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (schoudha@redhat.com), skipping review request. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/hold I need cri-o's go ahead first. |
/retest |
1 similar comment
/retest |
just confirming, non crio installation works fine as well with the new mounting path, right? |
Sure, I'm not removing the old mount of host's /proc. |
/hold cancel |
/retest |
# manage_network_ns_lifecycle determines whether we pin and remove network namespaces | ||
# and manage their lifecycle |
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.
nit: can we put this clause inside of the if statement?
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.
Ah right, I should, that's a template.
one nit, non blocking, otherwise LGTM, thanks @dulek |
cri-o is not complying with the CNI spec when manage_network_ns_lifecycle isn't set to "true". This affects Kuryr SDN so this commit enables that option when Kuryr is enabled. As in that more reliable mode network namespaces are placed in the standard /run/netns directory we need to mount it into kuryr-cni container in order to be able to access the network namespaces there. This commit does so too.
/retest /lgtm |
@dulek: This pull request references Bugzilla bug 1939605, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retest Please review the full test history for this PR and help us cut down flakes. |
18 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
More CI issues to investigate. |
/retest Just checking if it haven't fixed on it's own. @mtnbikenc: If it won't work, do you have an idea where to look for help? |
@dulek: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Based on this line in the job, I'm wondering if there is an issue because of the warning that user "ci-test" is not found.
The three ad-hoc Ansible commands succeed, but then the |
I'm still looking into ese-aws errors as I have time. I've discovered the xio.io service is offline and we depend on that for CI name resolution. I'll be testing some alternatives. |
e2e-aws should be fixed/ |
/hold cancel |
@dulek: All pull requests linked via external trackers have merged: Bugzilla bug 1939605 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
cri-o is not complying with the CNI spec when
manage_network_ns_lifecycle isn't set to "true". This affects Kuryr SDN
so this commit enables that option when Kuryr is enabled.
As in that more reliable mode network namespaces are placed in the
standard /run/netns directory we need to mount it into kuryr-cni
container in order to be able to access the network namespaces there.
This commit does so too.