With [1] OVN main branch compilation fails, until
main branch is fixed to work with ovs master, let's
ping OVS_BRANCH to working commit.
[1] https://github.com/openvswitch/ovs/commit/b8bf410
Closes-Bug: #1999154
Change-Id: I3453aa86cab4997ea22d0f8cb5c107871e171f67
We had 2 different kinds of "ovn ipv6 only" jobs defined:
- neutron-ovn-tempest-ovs-release-ipv6-only
- neutron-ovn-tempest-ipv6-only
First of them was running only smoke tempest tests and we had it
in our periodic queue.
Second was run in the check and gate queues and was running all tempest
networking related tests.
That second one was also installing OVS and OVN from sources instead of
the packages provided by the distro.
This patch unifies those 2 jobs so we now have
abstract "neutron-ovn-tempest-ipv6-only-base" and derived from that
2 different jobs:
- neutron-ovn-tempest-ipv6-only-ovs-release - used in check/gate queue,
- neutron-ovn-tempest-ipv6-only-ovs-master - used in periodic queue
Additionally this patch removes "neutron-ovn-tempest-ovs-release" job
from the periodic queue as it is now in the check/gate queue.
Change-Id: I355c5eaca31e12bf980794b1867e1ca39aea96e0
This job was run only in periodic queue until now but to avoid issues
like described in the related but, we should have this job run in
the check/gate queues as this is job which almost directly inherits from
the "tempest-integrated-networking" defined in the tempest.
Related-Bug: #1991962
Change-Id: I0ceaa9667a9218cb12a0f3b666a68d4bddeb6911
Added three new jobs:
* neutron-functional-with-oslo-master
* neutron-ovs-tempest-with-oslo-master
* neutron-ovn-tempest-ovs-release-with-oslo-master
These jobs will be executed in the "periodic" queue and will test the
Neutron repository with the oslo libraries installed from source
(master branch).
Closes-Bug: #1993498
Change-Id: Ie89a623a81642ab900a0ddb4c254319f6dcf049d
Bumped minimum OVN version of "neutron-ovn-grenade-multinode" job
to v21.06.0
Now "neutron-ovn-tempest-ipv6-only" and "neutron-ovn-rally-task" will
use this specific verison too, instead of using the default OS package
(in Ubuntu 20.04, the released package is v20.03.2).
Related-Bug: #1990229
Change-Id: I077a8409773ca4ad057cb45d446971a2c3a3703f
Only pep8 job is required to run on .pylintrc
changes, add .pylintrc to irrelevant-files for
all other jobs.
Change-Id: I6938dea3ee5e919a51083d50b19d1e3b54cda1db
Now it's better to use Centos Stream than Fedora as it should be more
stable and closer to RHEL really. So lets switch Fedora based
periodic/experimental job to the Centos 9 Stream.
Change-Id: I8aa5d563134b988afb6369a59fa76d44e1f6db6e
change Ib18efa3f472736b58c8967847b1061da0e3897d7
made linuxbridge an experimental feature but
it did not enable linuxbridge in the linuxbridge jobs
this job is used by both nova and devstack and perhaps
other project on an as needed basis. As a result
this is causing gate failures in neutron when some files
are modifed such as the netwroking module or vif.py files
This change enabled linux brdige in the base linux bridge
job and removes an old duplicate job defintion since
nova and devstack now use the new name.
Change-Id: I290027fbac47bd1df7bcdd08c405db107ed63db0
Closes-Bug: #1980948
This reverts commit 7c95150c84d77f3eae69def5b1328243ccec248a.
Reason for revert: The bug related to this change has been fixed for a while: https://bugs.launchpad.net/neutron/+bug/1906490
Change-Id: Icd8208d63be413f45fcd0c8652ab02a3a53ffc3a
This reverts commit a1384678b88fc7ffb5eeccfbfc0da16a9cb8910a.
Reason for revert: https://bugzilla.redhat.com/show_bug.cgi?id=2092856 fixed in libvirt-8.4.0-3.el9 and available in CentOS 9-Stream.
Change-Id: I2f33543fa7ee65ce3d25f70af49a18b69f799aec
Related-Bug: #1979047
Related-Bug: rhbz#2092856
libvirt-8.4.0-1.el9 caused a regression which resulted into
AttachInterfacesTestJSON and test_hotplug_nic tempest test to
fail, until fixed libvirt version is available in CentOS 9-Stream
repos, let's exclude these tests from jobs running
on CentOS 9-Stream.
Related-Bug: #1979047
Related-Bug: rhbz#2092856
Change-Id: Ia97fc084dcbdfbced0c2cc79f127a97b4d97d1e3
FIPS jobs reboot nodes after enabling FIPS,
but unbound service takes some time to
be ready and until then DNS resolution fails.
[1] added support to check DNS is ready after
reboot, in order to utilize it we need to
set "nslookup_target" job var.
[1] https://review.opendev.org/c/zuul/zuul-jobs/+/844704
Closes-Bug: #1978938
Change-Id: Ia39753f7cc533ba9959136b95bc3401d2f34cad4
Since these jobs do not use roles and playbooks for
configuring functional jobs let's add these
to irrelevant-files.
Needed By:- https://review.opendev.org/c/openstack/neutron/+/843252.
Change-Id: I79dcf96a2b0fdaeeb2e81501f2a546e5fadffa35
Changes in requirements.txt file should trigger all our CI jobs
to make sure that new requirements aren't breaking anything for sure.
This patch also removes test-requirements.txt from the irrelevant files
of the functional and fullstack jobs as those jobs are using
test-requirements.txt too so changes in that file should trigger those
jobs as well.
Change-Id: I150e80f1fac9c570bed39b2709635b73c57077e0
Those jobs from periodic pipeline were run on Centos Stream 8
so far but lets switch them to new Centos Stream 9.
Change-Id: I9d87d1c6d2c5415a4bd602cb6968db4d155f15e1
Seen couple of kernel panic issues in these jobs,
switch to cirros uec image to avoid it.
This is already done in non-scenario jobs defined
in neutron-tempest-plugin[1].
[1] https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/821067
Change-Id: Ic57f828c08f1793226759baedb3eb2f646191e1f
Currently when a job config is updated, all other
jobs are triggered unnecessary.
This patch updates irrelevant files to ignore changes
in all job config files except zuul.d/project.yaml(as
this contains the list of jobs to run not their definitions).
With this only the jobs whose definitions are updated(along with
it's child jobs) will be triggered because by default
match-on-config-updates is set to true for a job[1] and
that ignores files or irrelevant-files for a job inclusion.
[1] https://zuul-ci.org/docs/zuul/latest/config/job.html#attr-job.match-on-config-updates
Change-Id: Ida7c3ac974058769eb7ff901715e9b17a998bf79
Update irrelevant-files for non scenario jobs to
avoid unnecessary jobs, like skip ovs/linuxbridge
jobs on ovn related changes, same for non-ovn jobs.
Also skip running these jobs on functional and
fullstack tests changes.
Change-Id: Id127675793cfd3b9d4e7e328fde64f8595c7b00d
Add ML2/OVS and ML2/OVN tempest jobs with FIPS enabled.
Right now, the FIPS jobs run on Centos 8 stream.
For now those jobs are added to the experimental queue but
we should think about adding them to periodic maybe.
Co-Authored-By: Slawek Kaplonski <skaplons@redhat.com>
Depends-On: https://review.opendev.org/c/openstack/tempest/+/822560
Change-Id: I974c7d04d13a87bbbd4de6164578724a2cfd85cc
Without this port binding fails with below error:-
Network <nw> is type of vxlan but agent <host> or mechanism
driver only support ['gre', 'local', 'flat', 'vlan'].
Also fix permissions of /opt/stack/devstack in ml2 ovs testing
documentation and added these files to irrelevant-files to skip
running functional jobs as these files are not used in those jobs.
Related-Bug: #1934466
Change-Id: I3ca2ea19bf5e316e580669caab4c607447034a11
After discussing this topic again during the PTG I spent some time
checking our scenario jobs which runs in the check and gate queues.
After analysis this patch proposes to:
* remove neutron-ovs-tempest-slow job from both check and gate queue as
slow tests are already run also in the
neutron-ovs-tempest-multinode-full job,
* remove neutron-ovn-tempest-slow job from both check and gate queue as
slow tests are already run also in the
neutron-ovn-tempest-ipv6-only job - of course this job is using IPv6
instead of IPv4 but I don't really think it's big issue in that case,
neutron-ovn-tempest-slow job was multinode job, unfortunately
neutron-ovn-tempest-ipv6-only is single node job and for now it isn't
possible to make ipv6-only job to be multinode job so we will keep it
like single node job and hopefully move to be multinode job when zuul
will provide required data in the job's inventory,
* move neutron-ovn-tempest-ovs-release and
neutron-ovn-tempest-ovs-release-ipv6-only jobs to periodic queue - I
think that running those tests once per day should be enough.
Additionally this patch removes definition of the neutron-ovs-tempest-slow
and neutron-ovn-tempest-slow jobs are those jobs aren't used anywhere now.
Change-Id: I657881c319d425470277885545240d6a8b66a1f6
Add the following jobs to the experimental queue to test with
neutron-lib master:
- neutron-ovs-tempest-with-neutron-lib-master
- neutron-fullstack-with-uwsgi-with-neutron-lib-master
- neutron-functional-with-uwsgi-with-neutron-lib-master
Change-Id: I12c2381eef365f1249a3779685112cb682d752ee
In the OVN repo [1] there is no "master" branch anymore.
There is "main" instead and that patch reflects that change in
the Neutron repo.
[1] https://github.com/ovn-org/ovn
Change-Id: Ia666e78b748567a63484752c99856c46c22630ec
The CI job "neutron-ovn-tempest-ovs-master-fedora" should be the same
as "neutron-ovn-tempest-ovs-master" but executed in the Fedora nodeset.
Related-Bug: #1942913
Change-Id: I89700030dedab33c28baf95993206cf5cdd1e6d6
Only OVS agent uses os-ken library, makes sense that the CI job
testing it uses this backend.
Closes-Bug: #1933626
Change-Id: I8b2eb11dfae5bc67ee9c3629f609e4b461e0ad7c
All Neutron CI jobs (except for unit, functional and fullstack jobs),
have explicitly defined the network backend used:
- linuxbridge
- ovs
- ovn
That was discussed and approved during the Neutron CI meetings [1].
[1]https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-06-15-15.00.log.html
Change-Id: I036924f13b77dd5957ad5e60b9f536562deb9f05
It wasn't enabled for neutron-tempest-iptables_hybrid and
neutron-ovn-tempest-ovs-master-fedora and that patch
enables it in both of those jobs.
Change-Id: I73240679055b943caf46646440f9c325cf21faf3
This patch adds a new single node tempest job with OVN master branch to
the experimental pipeline because sometimes we need to test a feature
that is not yet included in the packaged version of OVN.
We do have a multi node job with OVN master branch in the experimetal
pipeline at the moment but, it's broken due to
https://review.opendev.org/c/zuul/zuul-jobs/+/762650. So it's no use at
the moment.
Depends-On: https://review.opendev.org/c/openstack/devstack/+/781971
Change-Id: I3f21ddc9ec97f2fa7ccb467893a37eb1b5342542
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
It should helps us understand why in some (rare) cases rule to redirect
packets send 169.254.169.254:80 to port 9697 isn't installed in the
qrouter namespace.
Change-Id: I644ea3d6767db36bfe7f4122ec2c2afe9888dd07
Related-Bug: #1920778
The OVN_BUILD_FROM_SOURCE was introduced by a patch in DevStack [0]
which allows for stacking OVN using packages instead of compiling it
from source (by default that flag is False). Now the jobs compiling OVN
(master ones) should include this flag.
Also since the logs are on different paths depending on how OVN is
installed, we are telling zuul to collect it properly for the compiled
version (this inconsistency is something that perhaps we should fix in
DevStack itself).
[0] https://review.opendev.org/c/openstack/devstack/+/763402
Change-Id: I46654762921aeec7603800005681239cdf202632
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
As jobs install OVN (and OVS) from package [0], this change removes potentially
confusing lines.
For folks interested in launching zuul jobs using a specific repo and
branch of OVN, use gerrit [1] as a reference. And do not forget to reply
with the comment 'recheck experimental' to trigger the job.
[0]: https://review.opendev.org/c/openstack/devstack/+/763402
[1]: https://review.opendev.org/c/openstack/neutron/+/763403
Change-Id: Iad88a56ea48475cb59b6684c528bcbb0c811761d
In this job (and this OS), deployment fails as ovsdb-server can not read
the tls certificates (it runs as openvswitch user and files are
user-readable only, owned by stack user). Disable tls-proxy service for
it, not needed anayway as it focuses on Neutron testing and not OVS.
Change-Id: Ibea391d503658ec738a60e34e19bdd6d809c845c
Closes-Bug: #1911128
OVN logs have moved from /var/log/openvswitch that is collected by the
base job to /var/log/ovn
Co-Authored-By: Lucas Alvares Gomes <lucasagomes@gmail.com>
Change-Id: I1e9fe661f55e99ca509dfbc3c1334b358ddb7212
This patch tries to make execution of the CI jobs in the Neutron
queue to be more smart. There is no need to e.g. run
linuxbridge scenario jobs job when only changed files in patch
are in e.g. the openvswitch agent module, or vice versa.
Change-Id: Ie33514da28991fa5952a1d8c289402ecb9ffee49
