The test validates that:
1.Two bandwidth limit rules could be both attached to a policy.
2.The system prevents addition of rules with the same direction to a policy.
Change-Id: I387d50673795c2a5073ec298426960fca593c017
Tests mostly run in parallel now, but this is not perfect yet. Set
concurrency to 1 until relatd bug is properly fixed
Change-Id: Ic3ed0c56c71a16cc6dcd2fc6f3c144c18e5be0ed
Related-Bug: #1851500
Related-Bug: #1660366
In neutron-tempest-plugin-dvr-multinode-scenario we had the same problem
as described in [1] for tempest multinode jobs. It was using python 3
on controller node but python 2 on all subnodes.
This patch changes that to use python3 on all nodes.
[1] https://bugs.launchpad.net/tempest/+bug/1853004
Change-Id: I9ef4daa821342d7462121a8bbde217ff5e0d7e9a
Related-Bug: #1853004
As was agreed during Shanghai PTG neutron-tempest-plugin jobs for queens
branch should always use tagged version of tempest and tempest-plugin
and should be removed from check/gate queues for patches to master
branch.
This patch is doing exactly that.
Change-Id: If1414baa0847d325da65f79248656a725cfe930b
This patch adds train jobs definitions to be run on stable/train branch.
It also reorders some definitions for stable branches to be in
chronological order.
Change-Id: I000563643d4a157102f5dd09cb2e855fb406a712
This job is now broken due to [1]. Revert for this patch is already
proposed in [2] but as this block all patches in neutron-tempest-plugin
repo, and there are in queue patches which should improve stability of
other neutron scenario jobs, lets not wait until [2] will be merged and
quickly unblock gates now.
[1] https://review.opendev.org/#/c/288271/
[2] https://review.opendev.org/#/c/691710/
Change-Id: I3951fa12a3b2c840ba2a11f22a298e7926aef649
Related-Bug: #1850626
Check that the DB registers returned by listing the network segment
ranges are the same as in single register retrieval (show vs list).
Change-Id: I9aee7f2a3108e605c203760a981ac226ecb33ea9
Related-Bug: #1828205
This test extends exisiting port_forwarding scenario test which
was only configuring and testing port forwarding to 2 different
servers using TCP protocol (by SSH to those instances to different
ports).
Now it also creates UDP port forwarding, spawns nc on each VM
and tries to connect to this nc and check if it will return proper
message from each VM.
Change-Id: I3afd877521e7cf66a8970f531111b3e1b1e7b150
For jobs running on stable branches we need to use API extensions
list correct for each branch.
This patch sets it for dvr and designate jobs where we somehow
missed it and used always extensions list from master branch.
Change-Id: I0c1dfe77711a2904850fb1a240eb7cf807722af6
The test verifies that admin user is able to set
DSCP marking rules with all of the valid marks between 0-56.
The test was moved from screnario\test_qos to api\test_qos.
Change-Id: I65b152622d4ba39ef710b44a2d3a044904e3e309
In test_agent_management some tests depend on one agent to be unmodified
which was not guaranteed as some tests updated that agent.
The update happened because the update test assumed that neutron will
return list of agents in different order.
The fix is only to select always different agent for update than the one
used for other tests.
Change-Id: I7af97ac0ee396d2eb132459d29e938bd5f3de9aa
Closes-Bug: #1845330
On Queens release by default iptables-hybrid firewall driver is used.
Using trunks with iptables-hybrid driver is not supported so we need
to skip test
neutron_tempest_plugin.scenario.test_trunk.TrunkTest.test_subport_connectivity
on Queens jobs.
Change-Id: Id212c35b71ca9e9af1ea546483c14fd597d895a8
Related-Bug: #1838760
We should run stadium projects jobs in gate queue for
neutron-tempest-plugin repo.
Job for networking-sfc was missing from gate queue so this
patch adds it there too.
Change-Id: I5b0d03fd0f8068ede749f416bec8d102d02308e7
Even though we do not test any actual port bindings, the lack of a
properly configured agent leads to errors in the server logs that may
cause confusion when trying to debug real issues.
So copy the setup from the openvswitch scenario jobs, which is the most
simple one.
Change-Id: I050aacbc1bacbadbd94359c1ab8f1ac721b90a12
This is step 1 of the movement of the tempest plugin for
neutron-dynamic-routing.
Co-Authored-By: Slawek Kaplonski <skaplons@redhat.com>
Change-Id: I35984bb3ad3673b7a54982657c1ac6fdc3ed6de0
When moving these tests to neutron-tempest-plugin, the jobs were
configured to run only on relevant files changes. Drop this restriction
so we check that any change to the repo will not break a stadium test.
This is in line with current configuration for bgpvpn and proposed one
for dynamic-routing
Change-Id: I81dc79150f2a7e2b099acad2e9a021d360dff799
In case of SSH timeout (TimeoutException, TimeoutError), the
tenacity.retry decorator retries the execution of the SSH
"execute" method up to 10 times.
Some SSH execute calls, related to QoS scenario tests, have been
enhanced by setting a relatively small timeout value. The commands
executed should be quick enough to be executed in this amount of time.
In case of timeout (due to communication problems), the retry decorator
will send again the command to be executed.
Change-Id: Idc0d55b776f499a4bc5d8c9d9a549f0af8f3fac0
Closes-Bug: #1844516
For example RHEL 8 image don't have Python installed by default,
so this test will fail when it should be skipped.
With this patch it will be skipped as before trying to start
multicast sender/receiver scripts, there is simple check if
python3 binary exists on VM.
Change-Id: I25cb5b159330ac80777f8ea784e98fa06e6e056f
Closes-Bug: #1842934
It will automatically set the router for cleanup, so use
it instead of admin_client.create_router().
Trivialfix
Change-Id: I7cff3f164dd76ba5e160cee4566732be10e9276d
Zuul
Miguel Lavalle
nfridman
Bernard Cafarelli
Slawek Kaplonski
Dirk Mueller
Rodolfo Alonso Hernandez
elajkat
Jens Harbott
Harald Jensås
Ryan Tidwell
pengyuesheng
Bence Romsics
Brian Haley
Cédric Ollivier