Skip to content

OCPBUGS-112789: [4.21] frr-k8s: use Recreate strategy for statuscleaner deployment - #3135

Merged
openshift-merge-bot[bot] merged 4 commits into
openshift:release-4.21from
andreaskaris:OCPBUGS-112789
Aug 25, 2026
Merged

OCPBUGS-112789: [4.21] frr-k8s: use Recreate strategy for statuscleaner deployment#3135
openshift-merge-bot[bot] merged 4 commits into
openshift:release-4.21from
andreaskaris:OCPBUGS-112789

Conversation

@andreaskaris

@andreaskaris andreaskaris commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Mainly clean cherry-pick of all commits from #3130.

Manual changes:

  • One minor conflict when cherry-picking frr-k8s: use Recreate strategy for statuscleaner deployment where git did not know what to do with the presence of function isSupportedDualStackPlatform which is present in 4.21 just before renderAdditionalRotuingCapabilities:
func isSupportedDualStackPlatform(platformType configv1.PlatformType) bool {
	return dualStackPlatforms.Has(string(platformType))
}

func renderAdditionalRoutingCapabilities(conf *operv1.NetworkSpec, bootstrapResult *bootstrap.BootstrapResult, manifestDir string) ([]*uns.Unstructured, error) {
(...)
  • needed to change context.Background() to t.Context() when cherry-picking apply: add unit tests for PrePatchAnnotation and replace fakeRESTMapper

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@coderabbitai

coderabbitai Bot commented Aug 24, 2026

Copy link
Copy Markdown

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: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 43262525-e36e-4719-b175-b55bd72e1e1f

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

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

@openshift-ci
openshift-ci Bot requested review from arkadeepsen and tssurya August 24, 2026 09:16
tpantelis and others added 4 commits August 24, 2026 17:57
This commit adds helper functions to testutil_test.go that are used
by component rendering tests to verify rendered Kubernetes objects:

- mustFindRenderedObj: Finds and converts unstructured objects using generics
- mustFindContainer: Finds a container by name in a container list
- findExecCommand: Extracts exec command strings from container command args

These utilities facilitate testing of rendered manifests and container
configurations across multiple components.

Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
Co-Authored-By: Ori Braunshtein <obraunsh@redhat.com>
(cherry picked from commit c617131)

Cherry-pick not clean:
- dropped definiton of mustFindContainer and findExecCommand (otherwise
  lint fails)

(cherry picked from commit cedf0d7)
The statuscleaner deployment uses hostNetwork with a fixed port (9123).
With the default RollingUpdate strategy, upgrades on SNO clusters get
stuck because the new pod cannot bind the host port already held by the
old pod. Switching to Recreate ensures the old pod is terminated before
the new one starts.

Signed-off-by: Federico Paolinelli <fpaoline@redhat.com>
Co-Authored-By: Ori Braunshtein <obraunsh@redhat.com>
Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
(cherry picked from commit 3d86b75)

Cherry-pick not clean:
- added bootstrap result wiring to additionalRoutingCapibilities (that
  was already there for 5.0), aligned existing unit test with
  fakeBootstrapResult() as in 5.0

(cherry picked from commit a5752d9)

Conflicts:
	pkg/network/render.go preserving
Very small conflict due to the presence of isSupportedDualStackPlatform.
Resolution: keep isSupportedDualStackPlatform + add bootstrapResult to
renderAdditionalRoutingCapabilities.
On upgrade, the frr-k8s-statuscleaner Deployment has rollingUpdate
fields defaulted by the API server. SSA cannot remove fields it does
not own, so switching strategy.type to Recreate fails with:

    spec.strategy.rollingUpdate: Forbidden: may not be specified when
    strategy `type` is 'Recreate'

Add a generic pre-patch annotation:

    networkoperator.openshift.io/pre-patch

that applies a strategic-merge-patch to the live object before SSA. This
lets the template atomically set type=Recreate and remove rollingUpdate
in a single patch, before SSA takes over.

Also explicitly set strategy to RollingUpdate with rollingUpdate fields
on non-SNO clusters so that CNO owns these fields going forward,
preventing the issue from recurring in case we have to make the same
switch for non-SNO clusters in the future.

Signed-off-by: Andreas Karis <ak.karis@gmail.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
(cherry picked from commit 8ebb78e)
(cherry picked from commit d59aba6)
Add tests for ApplyObject's pre-patch behavior: strategic-merge-patch
runs before SSA, NotFound is tolerated, other errors stop reconciliation,
and objects without the annotation skip pre-patch entirely.

Remove fakeRESTMapper and replace it with
testrestmapper.TetsOnlyStaticRESTMapper to return a proper mapper,
and return scheme.Scheme from Scheme(). Both changes needed by
ApplyObject under test.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Andreas Karis <ak.karis@gmail.com>
(cherry picked from commit 6ca59b1)
(cherry picked from commit b1775c9)

Not clean cherry-pick:
Make the linter happy by applying the changes to pkg/apply from
openshift#3138. See
that PR for further details.
@jechen0648

Copy link
Copy Markdown

/verified by pre-merge testing by @jechen0648

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 24, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@jechen0648: This PR has been marked as verified by pre-merge testing by @jechen0648.

Details

In response to this:

/verified by pre-merge testing by @jechen0648

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.

@andreaskaris

Copy link
Copy Markdown
Contributor Author

/pipeline required

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test frrk8s-e2e
/test 4.21-upgrade-from-stable-4.20-e2e-aws-ovn-upgrade
/test 4.21-upgrade-from-stable-4.20-e2e-azure-ovn-upgrade
/test 4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-upgrade
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-aws-ovn-upgrade
/test e2e-aws-ovn-upgrade-ipsec
/test e2e-aws-ovn-windows
/test e2e-azure-ovn-upgrade
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-dualstack-bgp
/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw
/test e2e-metal-ipi-ovn-ipv6
/test e2e-metal-ipi-ovn-ipv6-ipsec
/test e2e-ovn-ipsec-step-registry
/test hypershift-e2e-aks

@andreaskaris andreaskaris changed the title Ocpbugs 112789 OCPBUGS-112789: [4.21] frr-k8s: use Recreate strategy for statuscleaner deployment Aug 24, 2026
@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 Aug 24, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@andreaskaris: This pull request references Jira Issue OCPBUGS-112789, which is invalid:

  • expected the bug to target either version "4.21.z." or "openshift-4.21.z.", but it targets "4.22.z" 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:

Mainly clean cherry-pick of all commits from #3130.

Manual changes:

  • One minor conflict when cherry-picking frr-k8s: use Recreate strategy for statuscleaner deployment where git did not know what to do with the presence of function isSupportedDualStackPlatform which is present in 4.21 just before renderAdditionalRotuingCapabilities:
func isSupportedDualStackPlatform(platformType configv1.PlatformType) bool {
  return dualStackPlatforms.Has(string(platformType))
}

func renderAdditionalRoutingCapabilities(conf *operv1.NetworkSpec, bootstrapResult *bootstrap.BootstrapResult, manifestDir string) ([]*uns.Unstructured, error) {
(...)
  • needed to change context.Background() to t.Context() when cherry-picking apply: add unit tests for PrePatchAnnotation and replace fakeRESTMapper

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.

@andreaskaris

Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 24, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@andreaskaris: This pull request references Jira Issue OCPBUGS-112789, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.z) matches configured target version for branch (4.21.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-105556 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-105556 targets the "4.22.z" version, which is one of the valid target versions: 4.22.0
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jechen@redhat.com), skipping review request.

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.

@andreaskaris

Copy link
Copy Markdown
Contributor Author

/retest

@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 Aug 25, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 25, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Tests from second stage were triggered manually. Pipeline can be controlled only manually, until HEAD changes. Use command to trigger second stage.

@openshift-ci

openshift-ci Bot commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Aug 25, 2026
@andreaskaris

Copy link
Copy Markdown
Contributor Author

/retest-required

@openshift-ci

openshift-ci Bot commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

@andreaskaris: 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/4.21-upgrade-from-stable-4.20-e2e-azure-ovn-upgrade 216d5c2 link false /test 4.21-upgrade-from-stable-4.20-e2e-azure-ovn-upgrade
ci/prow/security 216d5c2 link false /test security
ci/prow/frrk8s-e2e 216d5c2 link false /test frrk8s-e2e
ci/prow/4.21-upgrade-from-stable-4.20-e2e-aws-ovn-upgrade 216d5c2 link false /test 4.21-upgrade-from-stable-4.20-e2e-aws-ovn-upgrade

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.

@openshift-merge-bot
openshift-merge-bot Bot merged commit d1d5e0e into openshift:release-4.21 Aug 25, 2026
25 of 29 checks passed
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@andreaskaris: Jira Issue Verification Checks: Jira Issue OCPBUGS-112789
✔️ 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-112789 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:

Mainly clean cherry-pick of all commits from #3130.

Manual changes:

  • One minor conflict when cherry-picking frr-k8s: use Recreate strategy for statuscleaner deployment where git did not know what to do with the presence of function isSupportedDualStackPlatform which is present in 4.21 just before renderAdditionalRotuingCapabilities:
func isSupportedDualStackPlatform(platformType configv1.PlatformType) bool {
  return dualStackPlatforms.Has(string(platformType))
}

func renderAdditionalRoutingCapabilities(conf *operv1.NetworkSpec, bootstrapResult *bootstrap.BootstrapResult, manifestDir string) ([]*uns.Unstructured, error) {
(...)
  • needed to change context.Background() to t.Context() when cherry-picking apply: add unit tests for PrePatchAnnotation and replace fakeRESTMapper

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.

@andreaskaris

Copy link
Copy Markdown
Contributor Author

/cherry-pick release-4.20

@openshift-cherrypick-robot

Copy link
Copy Markdown

@andreaskaris: new pull request created: #3140

Details

In response to this:

/cherry-pick release-4.20

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.

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.

7 participants