OCPBUGS-65688, OCPBUGS-66235: DownStream Merge [12-19-2025]#2910
OCPBUGS-65688, OCPBUGS-66235: DownStream Merge [12-19-2025]#2910openshift-merge-bot[bot] merged 98 commits intomasterfrom
Conversation
enable proper multi-arch fedora builds by building ovn-kubernetes inside the container build Signed-off-by: Killian Muldoon <kmuldoon@nvidia.com>
Signed-off-by: Ihar Hrachyshka <ihrachyshka@nvidia.com> Assisted-By: Claude Code; claude-sonnet-4-20250514
Signed-off-by: Dave Tucker <dave@dtucker.co.uk>
When a CPIC is created and the cloud controller externally sets its status to Failed because the node no longer exists ovn-k should clean it up. Reproducer: 1. CPIC assignment fails because the node was removed after the object was created but before it was sucessfully assigned in cloud. 2. The EgressIP status never reflects it as it ignores non-sucessfull assignments 3. Later reconciliation attempts trying to create the same CPIC again 4. Creation failures due to "already exists" errors To fix the issue remove failed CPICs during CPIC add reconciliation. Signed-off-by: Patryk Diak <pdiak@redhat.com>
In a scenario when during CPIC removal the EIP controller wants to assign it again we were missing a reconciliation attempt after the removal succeded. Signed-off-by: Patryk Diak <pdiak@redhat.com>
The default `all` target depended on non-existing targets. Signed-off-by: Ihar Hrachyshka <ihrachyshka@nvidia.com>
It was deprecated and has no effect. Signed-off-by: Ihar Hrachyshka <ihrachyshka@nvidia.com>
Wrap IPv6 addresses in brackets when constructing curl URLs, as IPv6 addresses with colons require bracket notation in URL syntax. Signed-off-by: Peng Liu <pliu@redhat.com>
…Exist refactor: don't panic in kind infra provider impl
fix: make -C dist/images
fix: multiarch fedora build
It includes the following important fixes (crashes): ovn-org/ovn@8a45709 ovn-org/ovn@62bf926 ovn-org/ovn@481e50c ovn-org/ovn@17f0502 Co-authored-by: Dumitru Ceara <dceara@redhat.com> Signed-off-by: Patryk Diak <pdiak@redhat.com>
…nd failure Add updateIPAMClaimStatus helper function to set IPAM claim status conditions for both successful and failed IP allocations. Previously, IPAM claim status was only updated on successful allocation. The new helper function: - Sets OwnerPod and IPs in status - Sets IPsAllocated condition (success/failure conditions) - failure conditions are: SubnetExhausted(ErrFull), IPAddressConflict (ErrAllocated), and ReserveMACConflict. the helper is called inside defer to make sure ipam.status.conditions are updated even in case of early return. defers in go run in LIFO so the rollback defer will run last, as it should. Signed-off-by: Ram Lavi <ralavi@redhat.com>
Add tests for IP conflict and IP exhausted ipamClaim status updates. Signed-off-by: Ram Lavi <ralavi@redhat.com>
add correct builder_image args for fedora image build Signed-off-by: Killian Muldoon <kmuldoon@nvidia.com>
Bump OVN to 25.09.2-2
fix: fix fedora image build
Enhance ipamclaim status update support
docs: Add backwards compatibility to OKEP template
Replace the hardcoded ARP proxy IP with the actual subnet gateway IP when configuring DHCP options for migratable KubeVirt pods. This ensures VMs receive the correct default gateway matching their pod's subnet configuration. On scenarios where the primary interfaces has multiple addresses the and there are some nftables masquerade rules, the address to masquerade with is choosen from the routing, so if the default gw is pointing to a link local address then the link local address of the of the interfaces will be choose as src ip, while the one that should be choose is the global address assigned as pod subnet on VM. Signed-off-by: Enrique Llorente <ellorent@redhat.com>
Signed-off-by: Nadia Pinaeva <n.m.pinaeva@gmail.com>
…dhcp-at-default-pod fix(kubevirt): Use pod network subnet gateway IP for DHCP router option
When building container images (e.g., fedora-image), the source directory is copied into the container build context. In git worktrees, the .git file is only a reference to the actual git directory, so git commands fail inside the container when the referenced path is not available. Add error suppression and fallback to "unknown" for GIT_COMMIT and GIT_BRANCH to allow builds to succeed. Also allow environment variable overrides for CI/CD systems. Signed-off-by: Peng Liu <pliu@redhat.com>
This does not actually work in non VRF-Lite configuration. When the BGP process attaches to the VRF to establish the BGP session, linux kernel assigns as source IP the IP of an interface attached to the VRF. In this case, the only available is management port IP. The session will fail as the remote peer cannot route back to that source IP. There are different options but overall we just need to add general support for host processes attaching to CUDN VRFs. For now, restrict the documentation to configurations we are actually testing. See: ovn-kubernetes/ovn-kubernetes#5580 Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
chore: Remove --disable-ovn-iface-id-ver
Remove the persistent IP requirement for enabling MAC conflict detection in layer2 UDNs. MAC conflict detection should be enabled when preconfigured UDN addresses are enabled, regardless of whether persistent IPs are enabled, making it consistent with IP conflict detection behavior. Signed-off-by: Patryk Diak <pdiak@redhat.com>
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
@qiowang721: This PR has been marked as verified by DetailsIn 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 |
openshift-ci-robot
added
jira/valid-bug
|
@jcaamano: This pull request references Jira Issue OCPBUGS-66235, which is valid. 3 validation(s) were run on this bug
DetailsIn 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. |
|
@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/okd-scos-images DetailsIn 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. |
|
/retest-required |
WOW! these 4.22 payload jobs all passed on the first try! I have never seen that before. Maybe it's a sign that 2026 will be the year of stable CI ?!?!?! |
|
/jira refresh The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity. |
|
@openshift-bot: This pull request references Jira Issue OCPBUGS-66235, which is valid. 3 validation(s) were run on this bug
DetailsIn 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. |
|
/retest-required |
|
azure-ovn-upgrade has passed on this PR before, but last three have failed. however, they failed for different reasons so I am not worried yet. according to sippy, the job is probably only a 60-70% pass rate right now, so guessing we are just getting unlucky. let's try again: /test e2e-azure-ovn-upgrade |
|
@openshift-pr-manager[bot]: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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-pr-manager[bot]: Jira Issue Verification Checks: Jira Issue OCPBUGS-66235 Jira Issue OCPBUGS-66235 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 DetailsIn 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. |
|
/retitle OCPBUGS-65688, OCPBUGS-66235: DownStream Merge [12-19-2025] |
openshift-ci
Bot
changed the title
|
@openshift-pr-manager[bot]: Jira Issue Verification Checks: Jira Issue OCPBUGS-65688 Jira Issue OCPBUGS-65688 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 Jira Issue OCPBUGS-66235 is in an unrecognized state (MODIFIED) and will not be moved to the MODIFIED state. DetailsIn 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 |
|
@qinqon: Jira Issue OCPBUGS-65688 is in an unrecognized state (MODIFIED) and will not be moved to the MODIFIED state. Jira Issue OCPBUGS-66235 is in an unrecognized state (MODIFIED) and will not be moved to the MODIFIED state. DetailsIn 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 |
|
@qinqon: Jira Issue Verification Checks: Jira Issue OCPBUGS-65688 Jira Issue OCPBUGS-65688 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 Jira Issue OCPBUGS-66235 is in an unrecognized state (MODIFIED) and will not be moved to the MODIFIED state. DetailsIn 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. |
|
Fix included in accepted release 4.22.0-0.nightly-2026-01-06-164201 |
|
/jira refresh |
|
@qinqon: Jira Issue OCPBUGS-65688 is in an unrecognized state (MODIFIED) and will not be moved to the MODIFIED state. Jira Issue OCPBUGS-66235 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state. DetailsIn 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. |
|
Fix included in accepted release 4.22.0-0.nightly-2026-03-15-203841 |
|
Fix included in accepted release 4.22.0-0.nightly-2026-03-17-033403 |
|
Fix included in accepted release 4.22.0-0.nightly-2026-03-19-202824 |
19 participants
Automated merge of upstream/master → master.