This reverts commit ffaf021810fcd8132582de544d3c324c3cc43b95.
Reason for revert: Fixed in oslo.serialization==5.5.0
Depends-On: https://review.opendev.org/c/openstack/requirements/+/926373
Change-Id: Ie09e230447f80b53a31bd1dad26e7f1722df2f30
Until the required fixes lands and release temporary
mark the job non-voting to unblock neutron gate.
Related-Issue: #2076430
Change-Id: I1044a5613e960bc24d63b7268f891abf1f223d28
All the ML2/OVS tempest jobs are now using the WSGI API
module, instead of the eventlet server.
Related-Bug: #2069581
Topic: eventlet-deprecation
Change-Id: I35d700885e6de0f1b92537789ae9819f8b21db0c
As was agreed on the CI meeting [1], this patch moves
neutron-ovn-grenade-multinode job from the experimental queue to the
check and gate queues.
Now in check/gate there are 2 grenade jobs: one ovs-multinode job and
one ovn-multinode job.
To not increase number of jobs in the check/gate, this patch also moves
neutron-ovs-grenade-dvr-multinode job to the periodic (and experimental)
queue.
[1] https://meetings.opendev.org/meetings/neutron_ci/2024/neutron_ci.2024-06-11-15.02.log.html#l-18
Change-Id: I22d0f9a59bca6f412dcf30005678229a859d5e4c
Commit 260c968118934 broke the gate by causing jobs
to not get run when it added RE2 compatibility for
irrelevant-files. Digging found that RE2 doesn't
support negative lookahead (and won't ever), so it's
impossible to replace the previous pcre filter with a
similar RE2 filter.
Instead of reverting to the original filter, which
is considered obsolete by zuul, this patch fixes the
issue by explicitly listing all files under zuul.d/
except the one that we actually want to trigger the
jobs: zuul.d/project.yaml.
Listing all the files in the directory for every job
is not ideal, and we may revisit it later, or perhaps
even reconsider the extensive use of irrelevant-files
in the neutron tree. This will have to wait for when
the gate is in better shape though.
[0] https://github.com/google/re2/issues/156
Related-bug: #2065821
Change-Id: I3bba89ac14414c6b7d375072ae92d2e0b5497736
As mentioned in the related bug we are seeing
hign memory usage in the job since sqlalchemy
bump to 2.0 and this leads to gate instability.
Adding some swap to handle this until the issue
is fixed.
Also reverts the concurrency reduction change[1]
that was done for this issue as that shouldn't be
needed now.
[1] https://review.opendev.org/c/openstack/neutron/+/920766
Related-Bug: #2065821
Change-Id: I33c4869c1d5230c0c8cc2f0dd4f6d071600bf220
Zuul has deprecated the usage of negative regex[1] and
reports WARNINGs when these are used.
This patch switches the branches regex to the supported
one.
[1] https://review.opendev.org/c/zuul/zuul/+/916141
Change-Id: I56a286cf33afb574436039128095e260539f63d9
The job can be affected by any patch landed in neutron-lib; the latter
repo doesn't run the job at all though.
We can add the job to neutron-lib check pipeline too (see bug referred
below), but more generally, we shouldn't gate on unreleased libraries.
The job is still extremely useful, but as advisory signal to anticipate
upcoming breakages.
Related-Bug: #2067515
Change-Id: Ia0be288b794b11659a5c98e4bd7c12a97c958926
Skip level jobs were wrongly upgrading from stable/2023.1.
As master is currently 2024.2, upgrade from branch should
be 2023.2, this patch fixes it.
Related-Bug: #2066221
Change-Id: I568ebb93bc009951ca113a09ee750982f580b40d
Seen couple of kernel panic issues in these jobs
even with libvirt_disable_apic=True workaround set.
switch to cirros uec image to avoid these issues.
Related-Bug: #1939108
Change-Id: Ib7f50f53368e2aea86ec47f73a1f8f50d9aac3be
Based on [0] only py39, py311 and py312 (non-voting) jobs
are in the testing runtime for 2024.2, updated relevant
files accordingly. Added timeout override for py312
similar to other versions.
[0] https://review.opendev.org/c/openstack/governance/+/908862
Change-Id: I6c3e94a88b7ef50b1fc74abe0ef4640ce3a68be3
During this release (non-SLURP), these jobs are now executed in the
"periodic" and "experimental" queues, but not the "check" queue.
Change-Id: If317cc0292e26339475192ce3bcca49ac5033e88
There are three job definitions here for testing
neutron with the master branches of other projects,
specifically neutron-lib, oslo, and ovsdbapp. As
neutron is no longer testing py310 in its master
gate, start using the py311 versions of these jobs
so we can move forward.
Also moved the sqlalchemy job to start using py311
as well.
Depends-on: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/899745
Change-Id: Iec1d5fcdfd8c85a3edb5bc9a399d44839fbc879a
This reverts commit 1d0335810d89ede47cf3b54614382cb25d1986ae.
Reason for revert: So we can look at a neutron DB
performance issue with devstack, see vPTG etherpad
for more info.
Change-Id: If2875caf9d14f1d13cee7e40b737e573252f0a7a
During the 2024.1 release, the lower version of grenade "skip-level"
jobs should be stable/2023.1.
During this release (SLURP), these jobs are now executed in the
"check" queue as voting.
Change-Id: I72ddd7657d219734bf44af38fc2f75e29bbc9547
The job names were changed but not replaced in the
"neutron-periodic-jobs" template.
This patch is also adding new binaries to the nftables installation
role, that includes all the "-save" and "-restore" ones.
Closes-Bug: #2039027
Change-Id: Ia4c140af74db29f4e40299648f1b5091b4801b51
This is the latest stable OVN release. As per the git submodule
command the required OVS version is v3.2.0-20-g1d78a3f31. This OVN
version contains additional_chassis column it its schema that is
required for functional testing of [1].
[1] https://review.opendev.org/c/openstack/neutron/+/895402
Change-Id: Idb564c589bd8f790bfcacd1b665780834b8fc686
Signed-off-by: Jakub Libosvar <libosvar@redhat.com>
Since [1] OVN/OVS source deploy jobs running with
OVN_BRANCH=main fails to compile ovn as this now
requires newer ovs commits from branch-3.2.
[1] https://github.com/ovn-org/ovn/commit/558da0cd
Closes-Bug: #2034096
Change-Id: I5247ce2b1a8606bde807a1744ed37daff04438f1
Until now neutron fullstack tests which were run by the same worker were
using same DB but after test content of the DB was cleaned.
This could cause problems e.g. for default security group rules which
weren't created properly in second test run by the same worker.
To fix that issue patch [1] was proposed and merged some time ago. But
this didn't solve the problem so this patch is effectively reverting [1]
and proposing another solution which will make each fullstack test to
use own DB and run db migration script.
As running DB migration before every test makes this jobs to run a bit
longer than it took before, this patch also increases timeout for the
fullstack job(s) to 3h (10800 seconds).
[1] https://review.opendev.org/c/openstack/neutron/+/891040
Related-bug: #1983053
Change-Id: Ia261b4c62db9a99ef6eb161acb4609520e45d101
Devstack already moved to it with [1] and it's working
fine, let's update in neutron jobs too.
[1] https://review.opendev.org/c/openstack/devstack/+/886162
Change-Id: I1f5cf34ad3e561670265caddbf2896d0a80fcada
Change-Id: I70144bfc30631a50d96058291947dc64787566ef
We agreed to have all periodic jobs in the experimental queue also to be
able to run them quickly if needed. And it was like that for most of the
jobs but jobs which came to the periodic queue from templates defined in
[1] were missing in the experimental queue.
This patch adds them to the experimental queue too.
Also added irrelevant-files to tox-py311 as it was
missing.
Related-bug: #2025753
[1] https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/zuul.d/project-templates.yaml
Change-Id: I933cfd66c22aeb0048e1a7c4717ffdf499f5b63c
It was agreed on the Neutron CI meeting [1] that we will remove
this job from check and gate queues and add it to the periodic queue
to run it once a day.
Linuxbridge agent is marked as experimental since at least one cycle
already and this scenario job is getting less and less stable now so
it's probably time to move it out from our gate.
[1] https://meetings.opendev.org/meetings/neutron_ci/2023/neutron_ci.2023-06-27-15.00.log.html#l-127
Change-Id: Ic9a808da8819c0cdbb4af6570fade5be2a9dacba
21.03 is no longer supported upstream. We should try to stick to LTS
releases of OVN if possible.
The patch locks the version as the latest git commit in branch-22.03
(ovs is also locked to the corresponding submodule version). This is
done to include a just merged fix for protocols used for ipv6 address
configuration (ra, na, mld*).
Once 22.03.3 is tagged in OVN repo, we can switch to it.
Depends-On: Id1328d7cba418fa7c227ae9db4fe83c09fd06035
Change-Id: I2a633741d5e95f0e46a6b33198903f0f44d449b6
