Skip to content

[release-4.20] OCPBUGS-81477: node: fix serviceUpdateNotNeeded nil pointer comparison#3099

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.20from
pliurh:release-4.20
Apr 15, 2026
Merged

[release-4.20] OCPBUGS-81477: node: fix serviceUpdateNotNeeded nil pointer comparison#3099
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.20from
pliurh:release-4.20

Conversation

@pliurh
Copy link
Copy Markdown
Contributor

@pliurh pliurh commented Mar 31, 2026

serviceUpdateNotNeeded() used explicit nil guards before dereferencing InternalTrafficPolicy and AllocateLoadBalancerNodePorts. When both old and new are nil (all non-LoadBalancer services), (nil != nil && ...) evaluates to false, incorrectly indicating an update is needed.

Use reflect.DeepEqual on the pointer directly, which handles nil == nil.

(cherry picked from commit 40caf4c) (cherry picked from commit 581bfde)

This is a clean manual cherry-pick.

📑 Description

Fixes #

Additional Information for reviewers

✅ Checks

  • My code requires changes to the documentation
  • if so, I have updated the documentation as required
  • My code requires tests
  • if so, I have added and/or updated the tests as required
  • All the tests have passed in the CI

How to verify it

serviceUpdateNotNeeded() used explicit nil guards before dereferencing
InternalTrafficPolicy and AllocateLoadBalancerNodePorts. When both old
and new are nil (all non-LoadBalancer services), (nil != nil && ...)
evaluates to false, incorrectly indicating an update is needed.

Use reflect.DeepEqual on the pointer directly, which handles nil == nil.

Signed-off-by: Peng Liu <pliu@redhat.com>
(cherry picked from commit 40caf4c)
(cherry picked from commit 581bfde)
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 31, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@pliurh: This pull request references Jira Issue OCPBUGS-81477, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-81475 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

serviceUpdateNotNeeded() used explicit nil guards before dereferencing InternalTrafficPolicy and AllocateLoadBalancerNodePorts. When both old and new are nil (all non-LoadBalancer services), (nil != nil && ...) evaluates to false, incorrectly indicating an update is needed.

Use reflect.DeepEqual on the pointer directly, which handles nil == nil.

(cherry picked from commit 40caf4c) (cherry picked from commit 581bfde)

📑 Description

Fixes #

Additional Information for reviewers

✅ Checks

  • My code requires changes to the documentation
  • if so, I have updated the documentation as required
  • My code requires tests
  • if so, I have added and/or updated the tests as required
  • All the tests have passed in the CI

How to verify it

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.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 31, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: 07cfd23b-aeb9-4bf7-957b-324df8ad2d5e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Note

.coderabbit.yml has unrecognized properties

CodeRabbit is using all valid settings from your configuration. Unrecognized properties (listed below) have been ignored and may indicate typos or deprecated fields that can be removed.

⚠️ Parsing warnings (1)
Validation error: Unrecognized key(s) in object: 'paths_ignore'
⚙️ Configuration instructions
  • Please see the configuration documentation for more information.
  • You can also validate your configuration using the online YAML validator.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@pliurh
Copy link
Copy Markdown
Contributor Author

pliurh commented Apr 1, 2026

/retest-required

@jcaamano
Copy link
Copy Markdown
Contributor

/lgtm
/approve
/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Apr 10, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 10, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 10, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcaamano, pliurh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 10, 2026
@SachinNinganure
Copy link
Copy Markdown

Scale test details
basic test:
API server restarts that cause service rule re-evaluation
Multiple service/pod configurations that would amplify the bug
verified no TCP RST packet floods
3 different tests were run with 100/160/480 pods and 20/35/105 services

Verified the scale and additional scenarios on the cluster with fix ; - The reflect.DeepEqual() fix in OVN-Kubernetes successfully prevents TCP RST storms

No RST packets generated during OVN pod restarts (trigger1)
No RST packets generated during API restarts (trigger2)

additionally conducted Service Resilience Validation Test which is API Restart Service Preservation Test
OVN watch loss and service resync events
Heavy traffic during serviceUpdateNotNeeded() timing windows
Customer-scale service configuration (16 external IPs, 4 TCP ports 10.157.2.10 through 10.157.2.25 and 80, 443, 15021, 30381 ports)
50+ external IPs and multiple TCP ports (as per cu setup)
Traffic Injection: Heavy concurrent connections during API restart window

1>All 16 external IPs maintained service preservation
2>0 service-specific RST packets seen
3>75-second downtime handled successfully(api outage)

@SachinNinganure
Copy link
Copy Markdown

/verified by @SachinNinganure

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 13, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@SachinNinganure: This PR has been marked as verified by @SachinNinganure.

Details

In response to this:

/verified by @SachinNinganure

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.

@arkadeepsen
Copy link
Copy Markdown
Member

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@arkadeepsen: This pull request references Jira Issue OCPBUGS-81477, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

@arkadeepsen
Copy link
Copy Markdown
Member

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Apr 14, 2026
@arkadeepsen
Copy link
Copy Markdown
Member

/retest-required

1 similar comment
@arkadeepsen
Copy link
Copy Markdown
Member

/retest-required

@deepsm007
Copy link
Copy Markdown

/test e2e-aws-ovn-serial

@arkadeepsen
Copy link
Copy Markdown
Member

/retest-required

@arkadeepsen
Copy link
Copy Markdown
Member

/payload 4.20 ci blocking
/payload 4.20 nightly blocking

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 14, 2026

@arkadeepsen: trigger 5 job(s) of type blocking for the ci release of OCP 4.20

  • periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-main-ci-4.20-e2e-gcp-ovn-upgrade
  • periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aks
  • periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fb2e4020-37fa-11f1-8b6f-25ef4e435303-0

trigger 9 job(s) of type blocking for the nightly release of OCP 4.20

  • periodic-ci-openshift-release-main-nightly-4.20-e2e-aws-ovn-serial-1of2
  • periodic-ci-openshift-release-main-nightly-4.20-e2e-aws-ovn-serial-2of2
  • periodic-ci-openshift-release-main-ci-4.20-e2e-aws-upgrade-ovn-single-node
  • periodic-ci-openshift-release-main-nightly-4.20-e2e-aws-ovn-upgrade-fips
  • periodic-ci-openshift-release-main-ci-4.20-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade
  • periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-ovn-conformance
  • periodic-ci-openshift-release-main-nightly-4.20-e2e-metal-ipi-ovn-bm
  • periodic-ci-openshift-release-main-nightly-4.20-e2e-metal-ipi-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fb2e4020-37fa-11f1-8b6f-25ef4e435303-1

@arkadeepsen
Copy link
Copy Markdown
Member

/retest-required

@arkadeepsen
Copy link
Copy Markdown
Member

/payload-job periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aks
/payload-job periodic-ci-openshift-release-main-ci-4.20-e2e-aws-upgrade-ovn-single-node
/payload-job periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-ovn-conformance

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 14, 2026

@arkadeepsen: trigger 3 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aks
  • periodic-ci-openshift-release-main-ci-4.20-e2e-aws-upgrade-ovn-single-node
  • periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-ovn-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/6e677e90-380e-11f1-9f56-3b4ac4f47013-0

@arkadeepsen
Copy link
Copy Markdown
Member

e2e-metal-ipi-ovn-dualstack-bgp failed on the step to release the lease after the e2e tests passed. Retrying the test one more time to get a green signal.

/test e2e-metal-ipi-ovn-dualstack-bgp

@arkadeepsen
Copy link
Copy Markdown
Member

/test qe-perfscale-payload-control-plane-6nodes

@arkadeepsen
Copy link
Copy Markdown
Member

/test e2e-aws-ovn-serial

@arkadeepsen
Copy link
Copy Markdown
Member

/test qe-perfscale-payload-control-plane-6nodes

@arkadeepsen
Copy link
Copy Markdown
Member

/payload-job periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aks
/payload-job periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-ovn-conformance

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 14, 2026

@arkadeepsen: trigger 2 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aks
  • periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-ovn-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/9f0af7b0-3819-11f1-8c9b-cdc0e73c43b9-0

@jluhrsen
Copy link
Copy Markdown
Contributor

/retest-required

@jluhrsen
Copy link
Copy Markdown
Contributor

/payload-job periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aks

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 15, 2026

@jluhrsen: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aks

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0ca4bc40-385e-11f1-9eea-2ff3583c91f6-0

@arkadeepsen
Copy link
Copy Markdown
Member

/retest-required

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 15, 2026

@pliurh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/security 2a5bf31 link false /test security
ci/prow/qe-perfscale-payload-control-plane-6nodes 2a5bf31 link true /test qe-perfscale-payload-control-plane-6nodes

Full PR test history. Your PR dashboard.

Details

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.

@arkadeepsen
Copy link
Copy Markdown
Member

/payload-job periodic-ci-openshift-release-main-ci-4.20-e2e-aws-upgrade-ovn-single-node
/payload-job periodic-ci-openshift-release-main-ci-4.20-e2e-azure-ovn-upgrade
/payload-job periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade
/payload-job periodic-ci-openshift-release-main-ci-4.20-e2e-gcp-ovn-upgrade

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 15, 2026

@arkadeepsen: trigger 4 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-ci-4.20-e2e-aws-upgrade-ovn-single-node
  • periodic-ci-openshift-release-main-ci-4.20-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-main-ci-4.20-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/3f0c9fb0-387f-11f1-9605-ee11d7e1b93b-0

@arkadeepsen
Copy link
Copy Markdown
Member

/payload-job periodic-ci-openshift-release-main-ci-4.20-e2e-azure-ovn-upgrade

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 15, 2026

@arkadeepsen: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-ci-4.20-e2e-azure-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/d028b930-388d-11f1-99b0-4601a89ccd18-0

@arkadeepsen
Copy link
Copy Markdown
Member

/test qe-perfscale-payload-control-plane-6nodes

@arkadeepsen
Copy link
Copy Markdown
Member

qe-perfscale-payload-control-plane-6nodes is failing due to auth error as there is network lock-down on the account. Slack thread: https://redhat-internal.slack.com/archives/CH76YSYSC/p1776234777981109?thread_ts=1776229952.898689&cid=CH76YSYSC

@jcaamano
Copy link
Copy Markdown
Contributor

/override ci/prow/qe-perfscale-payload-control-plane-6nodes

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 15, 2026

@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/qe-perfscale-payload-control-plane-6nodes

Details

In response to this:

/override ci/prow/qe-perfscale-payload-control-plane-6nodes

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.

@openshift-merge-bot openshift-merge-bot Bot merged commit b8b321e into openshift:release-4.20 Apr 15, 2026
29 of 30 checks passed
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@pliurh: Jira Issue Verification Checks: Jira Issue OCPBUGS-81477
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-81477 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

serviceUpdateNotNeeded() used explicit nil guards before dereferencing InternalTrafficPolicy and AllocateLoadBalancerNodePorts. When both old and new are nil (all non-LoadBalancer services), (nil != nil && ...) evaluates to false, incorrectly indicating an update is needed.

Use reflect.DeepEqual on the pointer directly, which handles nil == nil.

(cherry picked from commit 40caf4c) (cherry picked from commit 581bfde)

This is a clean manual cherry-pick.

📑 Description

Fixes #

Additional Information for reviewers

✅ Checks

  • My code requires changes to the documentation
  • if so, I have updated the documentation as required
  • My code requires tests
  • if so, I have added and/or updated the tests as required
  • All the tests have passed in the CI

How to verify it

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.