-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[release-1.33] : server: handle missing network namespace gracefully during networkStop #9337
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
[release-1.33] : server: handle missing network namespace gracefully during networkStop #9337
Conversation
After host reboot, network namespaces are destroyed but CRI-O attempts to clean them up during pod sandbox destruction, causing CNI plugin failures and preventing pods from restarting properly. The fix ensures pods can restart normally after host reboots. Signed-off-by: Sohan Kunkerkar <sohank2602@gmail.com>
…etns Signed-off-by: Sohan Kunkerkar <sohank2602@gmail.com>
Signed-off-by: Sohan Kunkerkar <sohank2602@gmail.com>
Kata VMs use real infra containers that persist in storage, unlike normal containers that use spoofed infra containers. This fundamental architectural difference means the 'Network recovery after reboot with destroyed netns' test scenario doesn't apply to Kata VMs in the same way. Signed-off-by: Sohan Kunkerkar <sohank2602@gmail.com>
@openshift-cherrypick-robot: Could not make automatic cherrypick of Jira Issue OCPBUGS-58229 for this PR as the target version is not set for this branch in the jira plugin config. Running refresh: /retitle [release-1.33] : server: handle missing network namespace gracefully during networkStop 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 openshift-eng/jira-lifecycle-plugin repository. |
@openshift-ci-robot: This pull request references Jira Issue OCPBUGS-58229, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
@openshift-cherrypick-robot: No Jira issue 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 openshift-eng/jira-lifecycle-plugin repository. |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: openshift-cherrypick-robot, sohankunkerkar The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## release-1.33 #9337 +/- ##
================================================
- Coverage 47.46% 47.41% -0.06%
================================================
Files 162 163 +1
Lines 24073 24103 +30
================================================
+ Hits 11427 11428 +1
- Misses 11528 11555 +27
- Partials 1118 1120 +2 🚀 New features to boost your workflow:
|
fcb351d
into
cri-o:release-1.33
This is an automated cherry-pick of #9301
/assign sohankunkerkar