As we are adding jobs for each stable branch, we have more and more jobs
there and it was very hard to maintain all of that in one single file.
So this patch reorganize it and places definitons in "per stable branch"
files.
Change-Id: I0e7816f4057c90bce90bca68137c077580f9426a
Ussuri branches are created already so it's time to start gating
them in the neutron-tempest-plugin too.
Change-Id: Ica7561c1d466bca87483cc82707664e567253703
Similarly to main tempest installation check, we should only install
plugin on master branches (where INSTALL_TEMPEST is True), and not on
stable branches
Also drop all-plugin use for tox_envlist in stadium jobs that were using
it, it is deprecated and breaks with this new variable
Change-Id: Ia7238c2044053d77b559de544c22909c50e1a11f
Co-Authored-By: Ghanshyam Mann <gmann@ghanshyammann.com>
Closes-Bug: #1873776
It seems that in case of scenario tests which uses advanced image, when
tests are run on slow node, it may happen that around 20 minutes test
timeout will be not enough to perform all cleanup after test and it will
fail due to that.
So lets give more time for such tests to make sure all will be cleaned
properly.
Change-Id: Ic2177dc90a6fc8db4b50f05649ad794f6c3d5a23
Closes-Bug: #1872693
Recent Rocky backports fail
neutron-tempest-plugin-scenario-openvswitch-iptables_hybrid-rocky job
and as mentioned in linked bug, this is expected as using trunks with
iptables-hybrid driver is not supported.
Add the test to the job blacklist
Change-Id: Iba083f66a4df8ecce23be07ec017d7dfc78406db
Related-Bug: #1838760
As was agreed during Shanghai PTG neutron-tempest-plugin jobs for the
branch which is going to EM phase should always use tagged version of
tempest and tempest-plugin and should be removed from
check/gate queues for patches to master branch.
Also skip two tests added for newer branches and unstable on rocky:
neutron_tempest_plugin.scenario.test_port_forwardings.PortForwardingTestJSON.test_port_forwarding_to_2_servers
neutron_tempest_plugin.scenario.test_security_groups.NetworkSecGroupTest.test_multiple_ports_portrange_remote
Change-Id: I9743bb950c434d8e0504492158a8bf3a305df401
This change introduces API tests of tagging ports during bulk creation.
Depends-On: I838de14f183f805c19411218edb815e190f8d650
Change-Id: I7ef0a92e73a15b2a9039b4fa97cecfefa5ba6aa3
Since Ib3bd70ba8f2e8386643c536ac8194fa99b54b842 and py2 testing drop,
this causes jobs in these branches to fail as designate-tempest-plugin
tries to install a python3-only version of dnspython
Use tag 0.7.0 for these branches, which is actually the previous commit
(so no changes in tests)
Also temporarily make neutron-tempest-plugin-bgpvpn-bagpipe non-voting,
it needs Ussuri beta releases and a networking-bagpipe fix [0]
[0] https://review.opendev.org/#/c/708648/
Change-Id: Ia2df06106419a45d56ff2de9193fe4e9c93ec62f
Closes-bug: #1864015
OpenStak ussuri release is python3-only which means
stable branhces jobs running on neutron-tempest-plugin
master gate should run with py3. neutron-tempest-plugin
will drop the py2 support soon so it will not be possible
to test the stable branch with py2.
Rocky jobs are modified to run on py2 on stable/rocky gate
and on py3 for master gate.
Change-Id: Ic04c9d1d2562398bd3640bfd064971bc82235502
It's temporary workaround until drop py27 support drama will be
finally gone. We need to unblock neutron-tempest-plugin gate to
merge patches related to newer branches.
Change-Id: I8e126d986918fd807edb09ed5c84cf225d58bf7f
In devstack install_Tempest, ref is taken by TEMPEST_BRANCH var[1]. TEMPEST_BRANCH var on zuul job
definitoin is priority than the default value in devstack[2]. When we set the queens compatible Tempest
tag[1] (with review style not by tag name) on devstack stable/queens, that is not taken by devstack
because neutron queens job define the smae with different value[4].
Also Tag name (for example queens-em) never work because of devstack logic. Tempest tag name only work
if RECLONE is true otherwise it should be gerrit ref style. So always Tempest master is installed
on queens jobs.
Let's remove the TEMPEST_BRANCH from neutron jobs and rely on devstack deafult value.
CLoses-Bug: 1859988
[1] https://github.com/openstack/devstack/blob/stable/queens/lib/tempest#L658
[2] 786c485cf6/stackrc (L313)
[3] https://review.opendev.org/#/c/703679/
[4] https://zuul.opendev.org/t/openstack/build/0cc32b278afe4e51b787d87d480f7092/log/job-output.txt#12370
Change-Id: I07beb6e7bdcbaf7ffe72d47f9edb90df40641e68
neutron-tempest-plugin tag 0.3.0 is for stable/queen which is
compatible with neutron-lib==1.13.0[1].
We are pinning Tempest and upper constraint used in tempest venv
for stable/queens which pickup neutron-lib as 1.13.0 from stable/queens
upper constraint.
Currently used tag of neutron-tempest-plugin 0.7.0 for queens job
is not compatible with stable/queens neutron-lib version. we can see
the failure[2]
Also skip the dns test for queens job which fixed went in 0.4.0 tag
(https://bugs.launchpad.net/neutron/+bug/1826419) and 0.4.0 tag is not
compatible with stable/queens constraint.
Related-Bug: 1859988
[1]f7b45b47bf/upper-constraints.txt (L58)
[2]
- https://6631124a20df425843c7-d8780b91d5409425c6866f467a1249cf.ssl.cf5.rackcdn.com/703680/3/check/neutron-tempest-plugin-api-queens/bba5f0e/job-output.txt
2020-01-23 17:36:50.747528 | controller | File "/opt/stack/neutron-tempest-plugin/neutron_tempest_plugin/bgpvpn/scenario/test_bgpvpn_basic.py", line 20, in <module>
2020-01-23 17:36:50.747537 | controller | from neutron_lib.utils import test
2020-01-23 17:36:50.747545 | controller | ImportError: cannot import name test
Change-Id: Icc4a91c333ac746183cb423f5e6c59ee0fbdfe2f
Those jobs are very unstable and caused problems with merging patches
not related to fwaas scenario tests too.
Change-Id: I1464a382c48bc95d12b8ec562d429401d3ab9d4a
Related-Bug: #1858645
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
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
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
Slawek Kaplonski