-
Notifications
You must be signed in to change notification settings - Fork 150
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-4.16] OCPBUGS-50594: fixes overzealous deletion of SNAT in egressIP #2456
base: release-4.16
Are you sure you want to change the base?
Conversation
@jluhrsen: This pull request references Jira Issue OCPBUGS-50594, 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. |
/jira refresh |
@jluhrsen: This pull request references Jira Issue OCPBUGS-50594, which is invalid:
Comment 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. |
/label backport-risk-assessed |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jluhrsen, trozet 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 |
@asood-rh: The label(s) 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-sigs/prow repository. |
/label cherry-pick-approved |
/ocpbugs cc-qa |
@asood-rh FYI I saw this PR, I was going to do pre-merge testing before labeling it |
@jechen0648 I did not see /ocpbugs cc-qa label added to PR when I added cherry-pick-approved, to indicate it is going to be pre merge tested. |
/label qe-approved |
/retest |
/hold |
currently when creating egressIP in a dualstack cluster regardless of if the egressip is ipv4 or ipv6 when disable-snat-multiple-gws is set the code removes both ipv4 and ipv6 snats from the database. This means that the pod will not be able to communicate with the cluster correctly becuase the Gateway Router is missing an SNAT and the traffic will be dropped. Additionally the testing looks a little different from the others because we do not correctly setup dualstack clusters when running unit tests Signed-off-by: Jacob Tanenbaum <[email protected]> (cherry picked from commit e64d754)
2f07cd5
to
ff27c7a
Compare
New changes are detected. LGTM label has been removed. |
@jluhrsen: This pull request references Jira Issue OCPBUGS-50594, which is valid. The bug has been moved to the POST state. 7 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), 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 openshift-eng/jira-lifecycle-plugin repository. |
/jira refresh |
@jluhrsen: This pull request references Jira Issue OCPBUGS-50594, which is valid. 7 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), 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 openshift-eng/jira-lifecycle-plugin repository. |
@jluhrsen: The following tests 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-sigs/prow repository. I understand the commands that are listed here. |
currently when creating egressIP in a dualstack cluster regardless of if the egressip is ipv4 or ipv6 when disable-snat-multiple-gws is set the code removes both ipv4 and ipv6 snats from the database. This means that the pod will not be able to communicate with the cluster correctly becuase the Gateway Router is missing an SNAT and the traffic will be dropped.
Additionally the testing looks a little different from the others because we do not correctly setup dualstack clusters when running unit tests
Signed-off-by: Jacob Tanenbaum [email protected]
(cherry picked from commit e64d754)
4.16 is not using ginkgo v2 so the new tests that came in from this PR using DescribeTable() and Entry() from v2 had
to be converted to ginkgotable.DescribeTable and ginkgotable.Entry()
additionally, there were two cherry-pick conflicts so the bot could not handle this and it was created manually.
which was resolved to just use:
ops, err = deletePodSNATOps(e.nbClient, ops, pod.Spec.NodeName, extIPs, affectedIPs)
which came down to the cherry-pick not able to de-dup three identical functions
buildEgressIPServiceAddressSets()
,buildEgressIPServedPodsAddressSets()
andbuildEgressIPNodeAddressSets()
.