On 10/4/23 13:32, Ales Musil wrote: > On Wed, Oct 4, 2023 at 1:23 PM Dumitru Ceara <[email protected]> wrote: >> >> Recently the ovn-kubernetes jobs failed often, mainly due to two >> reasons: >> - GitHub runners exhausting disk space >> - ovn-org/ovn job definitions being out of sync with >> ovn-org/ovn-kubernetes job definitions. >> >> This series tries to address both problems. In an ideal world >> ovn-kubernetes would also use tagged releases allowing us to pin >> the ovn-kubernetes version we're testing against to the latest >> stable version. That's not the case currently though. >> >> Ales Musil (2): >> ci: Handle google-cloud-sdk -> google-cloud-cli package name change. >> ci: Free up additional space for ovn-k jobs. >> >> Dumitru Ceara (3): >> ci: Free up disk space in a more robust way. >> ci: ovn-kubernetes: Reduce ovnkube pods log verbosity. >> ci: ovn-kubernetes: Synchronize CI jobs with ovn-org/ovn-kubernetes. >> >> >> .ci/linux-util.sh | 6 +++- >> .github/workflows/ovn-kubernetes.yml | 46 ++++++++++++++++++++++------ >> 2 files changed, 42 insertions(+), 10 deletions(-) >> > > > The whole series looks good to me, thanks! > > Acked-by: Ales Musil <[email protected]> >
Thanks, Ales! I'm going to wait with applying this series though because upstream ovn-kubernetes CI is unstable. CC: some ovn-kube community members I see a few options: a. reduce the set of ovn-kube tests we're running (either less lanes or go back to the subset we had before patch 5/5). b. skip an explicit list of tests from CI c. with help from ovn-kubernetes, tag a few of the tests as "unstable" in their repo and change our jobs to skip those in CI. d. add explicit versions (maybe just some git tags are enough) to ovn-kubernetes and pin ovn-kubernetes to the last stable version in our CI (this option is probably worth discussing widely in a separate thread). Regards, Dumitru _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
