On 10/14/25 5:09 PM, Dumitru Ceara wrote: > On 9/5/25 1:55 PM, Dumitru Ceara via dev wrote: >> Since [0] some feature tests have been moved out of the default >> "control-plane" CI lane in ovn-kubernetes. In order to run those, they >> have to be explicitly triggered. When that change happened the OVN CI >> lanes were not updated so we lost test coverage for those features. >> >> This lead to regressions like [1] creeping in. >> >> This commit re-enables the tests. >> >> [0] https://github.com/ovn-kubernetes/ovn-kubernetes/commit/cf116ea >> [1] https://mail.openvswitch.org/pipermail/ovs-dev/2025-September/426000.html >> >> Signed-off-by: Dumitru Ceara <[email protected]> >> --- > > I'm failing to reproduce the failure in my fork right now, even on the > same branch as ovsrobot. Triggering a retry in the robot's fork in case > that makes a difference. In theory nothing has changed since the last > time the jobs failed yet they don't seem to fail anymore.. > > Recheck-request: github-robot-_ovn-kubernetes >
Hi all, Now that the ovn-kubernetes CI test has been fixed [0] (thanks Tim!) and was backported [1] to ovn-k's release-1.1 branch, I rebased and posted a v2 of this patch [2]. Regards, Dumitru [0] https://github.com/ovn-kubernetes/ovn-kubernetes/pull/5656 [1] https://github.com/ovn-kubernetes/ovn-kubernetes/pull/5661 [2] https://patchwork.ozlabs.org/project/ovn/patch/[email protected]/ _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
