Skip to content

OCPBUGS-85711: Sync 2026-05-27#132

Merged
openshift-merge-bot[bot] merged 17 commits into
openshift:mainfrom
cgoncalves:sync-20260527
May 27, 2026
Merged

OCPBUGS-85711: Sync 2026-05-27#132
openshift-merge-bot[bot] merged 17 commits into
openshift:mainfrom
cgoncalves:sync-20260527

Conversation

@cgoncalves
Copy link
Copy Markdown
Contributor

Is this a BUG FIX or a FEATURE ?:

Uncomment only one, leave it on its own line:

/kind bug
/kind cleanup
/kind feature
/kind design
/kind flake
/kind failing
/kind documentation
/kind regression

What this PR does / why we need it:

Special notes for your reviewer:

Release note:


adilGhaffarDev and others added 17 commits March 25, 2026 15:57
Signed-off-by: Muhammad Adil Ghaffar <muhammad.adil.ghaffar@est.tech>
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
Add an optional LocalASN field to the Neighbor API type that instructs
FRR to advertise a different ASN to a specific peer via:
neighbor <peer> local-as <ASN> no-prepend replace-as

Signed-off-by: Muhammad Adil Ghaffar <muhammad.adil.ghaffar@est.tech>
bgp: add localASN field to Neighbor for per-peer local-as override
Signed-off-by: PseudoResonance <75700a85-1205-4740-aebf-4413a352e81b@otake.pw>
Signed-off-by: Federico Paolinelli <fpaoline@redhat.com>
Prepare the v0.0.24 release notes
Fix CRD ASN validation for K8s v1.36.0
Signed-off-by: Federico Paolinelli <fpaoline@redhat.com>
Prepare the v0.0.25 release notes
On IPv6 single-stack clusters where nodes have no IPv4 addresses, FRR
defaults the BGP router-id to 0.0.0.0. This violates RFC 6286 and
RFC 4271, causing remote peers to reject the session with "Bad BGP
Identifier".

Derive a deterministic router-id from the node hostname using CRC32
when no explicit router-id is configured, matching the approach already
used by MetalLB's native BGP implementation.

Signed-off-by: Carlos Goncalves <cgoncalves@redhat.com>
Generate fallback BGP router-id on IPv6-only nodes
@cgoncalves cgoncalves changed the title Sync 2026-05-27 OCPBUGS-85711: Sync 2026-05-27 May 27, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels May 27, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@cgoncalves: This pull request references Jira Issue OCPBUGS-85711, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @evgenLevin

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

Details

In response to this:

Is this a BUG FIX or a FEATURE ?:

Uncomment only one, leave it on its own line:

/kind bug
/kind cleanup
/kind feature
/kind design
/kind flake
/kind failing
/kind documentation
/kind regression

What this PR does / why we need it:

Special notes for your reviewer:

Release note:


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, evgenLevin and fedepaol May 27, 2026 08:02
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 27, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cgoncalves

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 May 27, 2026
@cgoncalves
Copy link
Copy Markdown
Contributor Author

/retest-required
Quay issues

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 27, 2026

@cgoncalves: all tests passed!

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.

@fedepaol
Copy link
Copy Markdown
Member

/lgtm
/verified by ci

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

@fedepaol: This PR has been marked as verified by ci.

Details

In response to this:

/lgtm
/verified by ci

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 added the lgtm Indicates that a PR is ready to be merged. label May 27, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit 99c313c into openshift:main May 27, 2026
7 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

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

Is this a BUG FIX or a FEATURE ?:

Uncomment only one, leave it on its own line:

/kind bug
/kind cleanup
/kind feature
/kind design
/kind flake
/kind failing
/kind documentation
/kind regression

What this PR does / why we need it:

Special notes for your reviewer:

Release note:


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. jira/severity-important Referenced Jira bug's severity is important 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