Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #301

/assign andreaskaris


The downstream bundle was missing this critical new parameter. Given
that disableMP is completely ignored now by both FRRK8s and by metallb's
built-in FRR, and given that dualStackAddressFamily always defaults to
false, dualStack AF setups were no longer possible in OpenShift.
Adding the parameter to the CRD fixes this issue.

Reported-at: https://issues.redhat.com/browse/CNF-21106
Signed-off-by: Andreas Karis <ak.karis@gmail.com>
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 15, 2026

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: CNF-21106

Details

In response to this:

This is an automated cherry-pick of #301

/assign andreaskaris


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 openshift-ci bot requested review from dougbtv and fedepaol January 15, 2026 16:26
@andreaskaris
Copy link

andreaskaris commented Jan 15, 2026

/rename CNF-21106 [release-4.21] CNF-21106: main: Downstream only: Fix broken downstream bundle

@andreaskaris
Copy link

andreaskaris commented Jan 15, 2026

/retitle CNF-21106: [release-4.21] CNF-21106: main: Downstream only: Fix broken downstream bundle

@openshift-ci openshift-ci bot changed the title [release-4.21] CNF-21106: main: Downstream only: Fix broken downstream bundle CNF-21106: [release-4.21] CNF-21106: main: Downstream only: Fix broken downstream bundle Jan 15, 2026
@fedepaol
Copy link
Member

/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 Jan 16, 2026
@openshift-ci
Copy link

openshift-ci bot commented Jan 16, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fedepaol, openshift-cherrypick-robot

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 Jan 16, 2026
@andreaskaris
Copy link

andreaskaris commented Jan 16, 2026

/retitle CNF-21106 [release-4.21] Downstream only: Fix broken downstream bundle

@openshift-ci openshift-ci bot changed the title CNF-21106: [release-4.21] CNF-21106: main: Downstream only: Fix broken downstream bundle CNF-21106 [release-4.21] Downstream only: Fix broken downstream bundle Jan 16, 2026
@andreaskaris
Copy link

/retitle OCPBUGS-73899[release-4.21] Downstream only: Fix broken downstream bundle

@openshift-ci openshift-ci bot changed the title CNF-21106 [release-4.21] Downstream only: Fix broken downstream bundle OCPBUGS-73899[release-4.21] Downstream only: Fix broken downstream bundle Jan 16, 2026
@andreaskaris
Copy link

/retitle OCPBUGS-73899 [release-4.21] Downstream only: Fix broken downstream bundle

@openshift-ci openshift-ci bot changed the title OCPBUGS-73899[release-4.21] Downstream only: Fix broken downstream bundle OCPBUGS-73899 [release-4.21] Downstream only: Fix broken downstream bundle Jan 16, 2026
@andreaskaris
Copy link

/refresh

@andreaskaris
Copy link

/retitle OCPBUGS-73899: [release-4.21] Downstream only: Fix broken downstream bundle

@openshift-ci openshift-ci bot changed the title OCPBUGS-73899 [release-4.21] Downstream only: Fix broken downstream bundle OCPBUGS-73899: [release-4.21] Downstream only: Fix broken downstream bundle Jan 16, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low 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 Jan 16, 2026
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-73899, which is invalid:

  • expected the bug to target the "4.21.0" version, but no target version was set
  • 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 Jira Issue OCPBUGS-73899 to depend on a bug targeting a version in 4.22.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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:

This is an automated cherry-pick of #301

/assign andreaskaris


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

andreaskaris commented Jan 16, 2026

/retitle CNF-21269: [release-4.21] Downstream only: Fix broken downstream bundle

@openshift-ci openshift-ci bot changed the title OCPBUGS-73899: [release-4.21] Downstream only: Fix broken downstream bundle CNF-21269: [release-4.21] Downstream only: Fix broken downstream bundle Jan 16, 2026
@openshift-ci-robot openshift-ci-robot removed jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 16, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 16, 2026

@openshift-cherrypick-robot: This pull request references CNF-21269 which is a valid jira issue.

Details

In response to this:

This is an automated cherry-pick of #301

/assign andreaskaris


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.

@karampok
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 16, 2026
@andreaskaris
Copy link

/retitle OCPBUGS-73900: [release-4.21] Downstream only: Fix broken downstream bundle

@openshift-ci openshift-ci bot changed the title CNF-21269: [release-4.21] Downstream only: Fix broken downstream bundle OCPBUGS-73900: [release-4.21] Downstream only: Fix broken downstream bundle Jan 16, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 16, 2026
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-73900, 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 Jira Issue OCPBUGS-73900 to depend on a bug targeting a version in 4.22.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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:

This is an automated cherry-pick of #301

/assign andreaskaris


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

/jira refresh

@openshift-ci-robot
Copy link

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

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.

@andreaskaris
Copy link

/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 Jan 16, 2026
@openshift-ci-robot
Copy link

@andreaskaris: This pull request references Jira Issue OCPBUGS-73900, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-73901 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-73901 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
  • bug has dependents

Requesting review from QA contact:
/cc @asood-rh

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.

@openshift-ci openshift-ci bot requested a review from asood-rh January 16, 2026 10:06
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-low Referenced Jira bug's severity is low 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants