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
This reverts commit 9651c635b7ab412074b9366633a8bd20589ef91e.
Reason for revert: oslo.policy 3.6.1 have fix for our performance
degradation when secure rbac are used. So it is good to make rally
job voting again.
Change-Id: I6839a1c98ea00d827ba54e86864c3faa6bb3a031
Tempest replaced the below rolevar for run-tempest role
- tempest_test_blacklist is replaced by tempest_test_exclude_list
- tempest_black_regex is replaced by tempest_exclude_regex
old name are still supported for compatiblity but we recommend
to switch to new one.
Depends-On: https://review.opendev.org/c/openstack/tempest/+/774835
Change-Id: I609c1714a4f630207562a4725456d3d7f87d698e
This job was moved to the experimental gate due to gate failures with
the multinode setup. Those failures are now fixed.
Change-Id: I4a5cb5d7085043b1a4e0e31bb793229a32290010
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
It was run on 3 nodes but I think there is no real need for that.
Running that on 2 nodes should be enough.
Change-Id: I12406c1f654ba9ad8eb60ffc965293ecbd5b7be5
The job neutron-tempest-with-neutron-lib-master is mostly to check if
current neutron changes will work fine with some changes done in
neutron-lib.
It isn't really needed to run it on all patches and can be rune on
demand by running experimental queue if that is needed.
This patch also removes job neutron-ovn-tempest-ovs-master from the
experimental queue as we already have there similar multinode job.
As job neutron-ovn-tempest-ovs-master wasn't used anywhere, this patch
also removes its definition.
Finally this patch improves ci_scenario_jobs document and adds there
info about experimental queue and what is there currently.
Change-Id: I0fc4ffd5db2673cefcd01307555d1a3900bb12e8
It's easier to check what was wrong if jobs in periodic queue
are voting.
It will not block any development so it is safe to do that.
Change-Id: I038f83afb1fd47de8570f526e594c4c69f4bfe19
We need to fix bug [1] and then make this job voting again.
But for now lets unblock the gate by making it non-voting
temporary.
[1] https://bugs.launchpad.net/neutron/+bug/1913718
Change-Id: I1129132967895cd59b0576db82a2ff659c778493
Related-Bug: #1913718
We don't need to run e.g. functional, fullstack and all scenario jobs
on patches which are changing e.g. only documentation or release notes
or other things like that.
This patch also removes test-requirements.txt and requirements.txt files
from that list of unrelated files as we want to run our ci jobs when
requirements are changed.
Change-Id: I7950de04c497b14d9225abe6584b7bb7d056f79c
To use less infra resources by every Neutron patch, let's move
co-gating jobs, like Ironic, Openstacksdk and Tripleo based jobs
to the periodic queue.
Those jobs will be still run daily so we should have pretty good
coverage if (and when) some neutron change broke those projects but
we will use less infra resources by running jobs for every patch
proposed to Neutron.
Change-Id: I91c55c9151a11401bd3a7fbe94e378a027bc97df
To give some relief to Zuul resources, lets move non-voting
jobs which are broken and failing all the time to the experimental
queue for now.
We can bring them back to check queue when we will fix them.
Change-Id: I4c4dd7a17ea7cc483bb4b3ed7cff7ee91f917ed9
neutron-tempest-dvr-ha-multinode-full job's computes seems to lack
resource_provider_bandwidths values set, let's see if it solves the
issuse with test_migrate_with_qos_min_bw_allocation and
test_resize_with_qos_min_bw_allocation.
Change-Id: Ie02f9d40716af1b3b4efc3e9340acab7f9af113e
In neutron CI queues we were running tempest-slow-py3 and
tempest-ipv6-only jobs which are defined in tempest repository and runs
all tests, e.g related to Swift or Cinder.
This patch defines new jobs: "neutron-tempest-slow-py3" and
"neutron-tempest-ipv6-only" which inherits from the tempest jobs but
disables Cinder and Swift services.
Additionally "neutron-tempest-ipv6-only" job now runs only
"integrated-networking" tox_envlist.
Change-Id: Icd376c144e1993ca84890c76743fda4196662d9b
The goal of this patch is to avoid the connection disruption during
the live-migration using OVS. Since [1], when a port is migrated,
both the source and the destination hosts are added to the profile
binding information. Initially, the source host binding is activated
and the destination is deactivated.
When the port is created in the destination host (created by Nova),
the port was not configured because the binding was not activated.
The binding (that means, all the OpenFlow rules) was done when Nova
sent the port activation. That happend when the VM was already
running in the destination host. If the OVS agent was loaded, the
port was bound seconds later to the port activation.
Instead, this patch enables the OpenFlow rule creation in the
destination host when the port is created.
Another problem are the "neutron-vif-plugged" events sent by Neutron
to Nova to inform about the port binding. Nova is expecting one single
event informing about the destination port binding. At this moment,
Nova considers the port is bound and ready to transmit data.
Several triggers were firing expectedly this event:
- When the port binding was updated, the port is set to down and then
up again, forcing this event.
- When the port binding was updated, first the binding is deleted and
then updated with the new information. That triggers in the source
host to set the port down and the up again, sending the event.
This patch removes those events, sending the "neutron-vif-plugged"
event only when the port is bound to the destination host (and as
commented before, this is happening now regardless of the binding
activation status).
This feature depends on [2]. If this Nova patch is not in place, Nova
will never plug the port in the destination host and Neutron won't be
able to send the vif-plugged event to Nova to finish the
live-migration process.
Because from Neutron cannot query Nova to know if this patch is in
place, a new temporary configuration option has been created to enable
this feature. The default value will be "False"; that means Neutron
will behave as before.
[1]https://bugs.launchpad.net/neutron/+bug/1580880
[2]https://review.opendev.org/c/openstack/nova/+/767368
Closes-Bug: #1901707
Change-Id: Iee323943ac66e566e5a5e92de1861832e86fc7fc
To limit usage of resources (mostly memory) in the fullstack job and
to avoid oom killer to kill e.g. mysqld service, this patch:
* Makes number of API workers changeable by tests, as a parameter to
EnvironmentDescription and defaults its value to 1. As neutron server
is spawned separately for each test and is used only to process just
few API requests during that single test so this should be still
enough there, and where more API workers are needed (like some dhcp HA
tests: TestDhcpAgentHARaceCondition) it can be changed,
* reduces number of test run workers from 4 to 3 - job will run slower
but hopefully more stable,
* in the functional and fullstack tests job definition disable etcd3
service - this will not save us a lot of memory but still it's not
needed at all so why to run it there.
Change-Id: If19803ab6db144e2d17d6805d379c1c76d8fa343
Closes-Bug: #1906366
It's blacklisted due to related bug. When the bug will be fixed we
should restore this test to be run in the gate.
Change-Id: I67df1820bfd681de44b8568b46cbc95dd940c024
Related-Bug: #1906490
After [1] we are now testing neutron with uwsgi in the
neutron-tempest-plugin-api job so there is no need to run
neutron-tempest-with-uwsgi in the check and gate queue anymore.
[1] https://review.opendev.org/761611
Change-Id: I5308a5f51a5700394c6b743c44159f30b526c655
We don't need to run Swift, Cinder and etcd services in the
Neutron jobs so this patch disables those services on all
such jobs defined in the Neutron repository.
It will skip some tests which aren't really related to Neutron
and will safe some resources on test nodes.
This patch also enables br-ex-tcpdump and br-int-flows services
in the jobs where it was missing.
It may be useful during debugging some failures of those jobs
in the future.
Depends-On: https://review.opendev.org/762622
Change-Id: I0db516b184cf621e4539d11726fe1bd47b53ba05
Now that these job depend on tripleo-ci-centos-8-content-provider job to
run, they should have the same list. Else, these jobs will try to run
while the parent one did not, generating zuul errors as seen for example
in [1]
[1] https://review.opendev.org/#/c/763218/
Change-Id: I2bf2d25f6a6f651a740578e92720676975f8283f
This patch removes jobs:
neutron-tempest-linuxbridge
neutron-tempest-iptables_hybrid
from the Neutron check and gate queues.
Most of the test run there are not backend dependent and they are run in
the neutron-tempest-multinode-full-py3 job too.
Some tests which may be impacted by different backend/firewall driver
are added to the neutron-tempest-plugin-scenario jobs now.
Additionally this patch removes also
neutron-tempest-plugin-dvr-multinode-scenario from the docs summary as
this job is not run in the check queue for some time now (it's moved to
the experimental queue).
Depends-On: https://review.opendev.org/#/c/761410/
Change-Id: Ica669e05f719568dad74c4e8bd69ddceadccea7e
This job neutron-ovn-tempest-ovs-release-ipv6-only was
broken due to a os-vif misconfiguration which is now fixed by
https://review.opendev.org/#/c/753575.
Change-Id: I7c89659e0de130f0c4b720ee7489d895a308f69d
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
We don't need it to test cinder in our jobs.
This patch disables Cinder in grenade jobs. If that will be ok
we can do the same for scenario jobs also.
This patch also enables br-ex-tcpdump and br-int-flows
services in the grenade jobs as it was missing there and
may be useful during debugging some failures of those jobs
in the future.
Change-Id: If490da1f7e695564a65cabf95f25c72f7639ae19
Tobiko is the testing framework which allows to do kind of "white box"
scenario testing. More info about it can be found at [1].
By adding devstack-tobiko-faults-centos job to out periodic queue we
will improve test coverage of our code as tobiko is testing e.g. L3ha in
that job. It also runs some scenarios, like e.g. restarting agents on
nodes, which can't be tested with tempest jobs.
[1] https://tobiko.readthedocs.io/en/latest/
Change-Id: I157645ed6d048de676dad5b2a93ab83a82880610
Content provider job builds and shares the artifacts among
consumer jobs. This removes dependency on docker.io pulls.
Change-Id: Ib2b9f541e6e287c3b0bfd091310e3ce267fc6adb
