[stable/wallaby] neutron-tempest-plugin-scenario-ovn-wallaby fails on ovn git clone

[Bernard Cafarelli]

Since 2023-06-30, the neutron-tempest-plugin-scenario-ovn-wallaby started to fail 100% in stable/wallaby backports:
https://zuul.opendev.org/t/openstack/builds?job_name=neutron-tempest-plugin-scenario-ovn-wallaby&project=openstack/neutron

Sample failure grabbed from https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_288/887253/2/check/neutron-tempest-plugin-scenario-ovn-wallaby/288071d/job-output.txt

2023-06-30 11:00:07.584319 | controller | + functions-common:git_timed:644 : timeout -s SIGINT 0 git clone https://github.com/ovn-org/ovn.git /opt/stack/ovn --branch 36e3ab9b47e93af0599a818e9d6b2930e49473f0
2023-06-30 11:00:07.587213 | controller | Cloning into '/opt/stack/ovn'...
2023-06-30 11:00:07.828809 | controller | fatal: Remote branch 36e3ab9b47e93af0599a818e9d6b2930e49473f0 not found in upstream origin

I think I recall some recent fixes (to devstack maybe) to change git clone/checkout, is it related and just a missing backport to wallaby? Newer branches are fine

[yatin (yatinkarel)]

It is triggered by https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/880889. And was not cached in CI as wallaby and before are extended maintenance and those jobs don't run in ntp patches.

Yes it was missing backport https://review.opendev.org/q/Id1328d7cba418fa7c227ae9db4fe83c09fd06035, i just pushed for wallaby and victoria(that too i think will be impacted)

Other option can be to pin victoria/wallaby jobs to working OVN_BRANCH.

[Rodolfo Alonso (rodolfo-alonso-hernandez)]

Fixed in https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/888029.