The job has been stable, shows failure percentages within a percent or
two of the neutron-tempest-iptables_hybrid job, and is forward looking
for the next version of RHEL/Centos.
Change-Id: Iafccd55269b64d29aee081f096f6352ab5c15430
Until related bug will not be fixed, grenade jobs are failing quite
often. Lets make them non voting to make our life easier.
This can be reverted when related bug will be fixed.
Change-Id: Iefe8d6ab2eea3e04e40cbf4ffaf0c646b51834c4
Related-Bug: #1820892
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I4c9b513eb65ec4c50bdb9a66dfcc676360bdaa28
This patch removes also legacy playbooks used before by
this experimental job and it also removes
neutron/tests/contrib/post_test_hook.sh script as it was used
only by functional and fullstack tests and it's not used anymore.
Change-Id: Ibc48ce8e80e11dcbb13da121aa86bbf01b98a3d9
Related-Bug: #1804844
Now, as neutron-functional job is moved to zuulv3 syntax,
the same can be easily done with fullstack job.
This patch also switches experimental neutron-fullstack-with-wsgi
job.
This patch removes also fullstack part from gate scripts
and it removes hooks for dstat and stack_base as both are not
used anywhere else.
Related-Bug: #1804844
Change-Id: Iac7583f01651410a3df3e349b2c843b109a8bb18
This patch migrates also neutron-functional-python27 job to
zuul v3 syntax.
Neutron's functional tests have to be run on host with
deployed minimal devstack but without running any e.g. neutron
services. Because of that new job's template inherits from
devstack-minimal job instead of devstack-tox-functional and
we need to have own run_functional_job and post_functional_job
playbooks.
It also adds ansible roles:
- configure_functional_tests
- setup_logdir
- fetch_journal_log
which are used in new neutron-functional job definition.
Those roles can be also used later e.g. for fullstack job.
Change-Id: I80bc17c8c9f43050ac0c21176fbc4be46c11ce35
Related-bug: #1804844
This patch migrates definition of
neutron-tempest-dvr-ha-multinode-full job to zuul v3 syntax.
Additionally this patch sets l3_ha config option in neutron
to True to make sure that routers created in tests are HA
always.
Change-Id: I3e48c5109dddc2fca6f3b9c289f416ed4a018a41
Related-Bug: #1804844
As seen in [0], openstacksdk uses a scenario for testing that isn't
currently covered by Neutron's own testing. Add a job from their stack
to be run on all patches, but make it non-voting to start with.
[0] https://bugs.launchpad.net/neutron/+bug/1816771
Change-Id: I35ba7664335026ca2a4d361d93fbf784bf0ffe5c
Related-Bug: 1816771
Related-Bug: 1817045
This patch switches tempest-slow to new
tempest-slow-py3 job.
Depends-On: https://review.openstack.org/633983
Change-Id: Ic4162f56294a4b6c9f3773964598e1fa163aad95
This patch switches tempest-multinode-full to new
tempest-multinode-full-py3 job.
Depends-On: https://review.openstack.org/633982
Change-Id: Iaca3b2a58c44af4c7684caeaf241ba05ef67a70a
As a part of the python 3 community goal, this converts the functional
tests to run with python3 by default, and in Zuul.
As discussed at the Stein PTG in Denver, unit and functional tests will
still run on both versions, so this adds a python2 job for functional
tests.
This patch also suppress logging levels from some external libraries
to avoid issues with subunit.parser and python 3. For details see bug
reported for Cinder [1].
[1] https://bugs.launchpad.net/cinder/+bug/1728640
Co-Authored-By: Slawek Kaplonski <skaplons@redhat.com>
Change-Id: I8958d0b5b9147ffd1ef2d1cef5dcbf79c8be5cd4
'integrated-gate-py35' template is going to be
renamed to 'integrated-gate-py3' in https://review.openstack.org/#/c/626078/
Integrated jobs are running on Bionic now where python 3.6 is available.
Which means gate jobs in 'integrated-gate-py35' template are
running on python 3.6 not on 3.5 which makes this template name confusing.
depends on commit rename the 'integrated-gate-py35' to 'integrated-gate-py3'
so that it can convey that template will use available python 3 version
in used distro. For example: 3.5 in xenial and 3.6 in bionic and so on.
This commit starts using the new template name so that old
template name can be removed.
Depends-On: https://review.openstack.org/#/c/626078/
Change-Id: Id14b1f46a6d98e284d97149287245dd59ca198c4
Change the name of the job to match the change for zuulv3
Depends-On: https://review.openstack.org/#/c/629173/
Change-Id: I6ee36b6fe0eb8043dc22a6906066a2611f7d7c74
Job neutron-tempest-iptables_hybrid was previously converted to
zuulv3 syntax but it inherited from devstack-tempest job.
It's better to inherit from proper job which already have configured
good "tox_envlist" and version of python which should be used.
Change-Id: I686386c48fabebb77813c4284f234f2ee3cb4024
Related-Bug: #1804844
This patch also removes config of osprofiler middleware in api-paste.ini
file in neutron-tempest-iptables_hybrid job as this middleware is
currently enabled by default.
Change-Id: Ifd3fdc33ba5c489618a568cccc20ee14e7d600a6
Proper fix in os-vif [1] is already merged and released in
os-vif 1.13.1 so we should be good now.
[1] https://review.openstack.org/#/c/624831/
This reverts commit 462b510c50081464c23d837b6b8d5ad8a1405331.
Change-Id: I3afdeaa7463d05e5cbd2d593715b1e2f25749586
Because of bug [1] neutron-tempest-iptables_hybrid job
is failing 100% times.
As we decided on Neutron CI meeting, lets make it non-voting
and remove it from gate queue temporary to unblock all
other patches until this bug will be fixed.
[1] https://bugs.launchpad.net/os-vif/+bug/1807949
Change-Id: Ic3a43629bb924e3ae48b919c6fd518674a530bbb
Related-Bug: 1807949
The standards state that if a job is voting in the check queue, it
should also be voting in the gate queue. The tempest-slow job is voting
in check, so therefore this change adds it to the gate queue.
Change-Id: I4221e587f5afc40304e7efc2dd53e937085d691b
In experimental queue there were some jobs which are already covered
by jobs which runs in check queue, so we don't need them in experimental
too.
Removed jobs:
tempest-pg-full -
covered by neutron-tempest-postgres-full from peridoic queue
legacy-tempest-dsvm-neutron-with-ryu-master -
covered by neutron-tempest-with-ryu-master from periodic queue
legacy-neutron-dsvm-api-pecan and legacy-tempest-dsvm-neutron-pecan -
pecan hook is droped by patch [1] so there is no way to
run it anymore
legacy-grenade-dsvm-neutron-forward - it is not needed in master branch,
this job is testing upgrade from N to N+1 release so it makes sense
to run it only on patches proposed to stable releases
[1] https://review.openstack.org/#/c/485825/
Change-Id: I1a632cb2fbc369c3ac949bd979fd0e96272931db
According with the ML thread [0] it was decided during the PTG in
Denver that Stadium projects are now allowed to add a non-voting job to
Neutron's check pipeling.
This patch is then adding a tempest job for the networking-ovn project.
[0]
http://lists.openstack.org/pipermail/openstack-dev/2018-September/135273.html
Depends-On: I49a644631365465ba4fbe2ca864dfa3d018c4b56
Change-Id: I4b7e7677b0f161048b7350cd491aba9e72d6b1d0
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
In the Neutron CI meeting on 2018-10-02 [1] we decided on the proper
approach for fullstack testing of Neutron in Zuul. The approach is:
1. There should be only one fullstack CI job, named "neutron-fullstack"
2. The neutron-fullstack job should invoke python3 in tox.ini
This change implements the agreed-upon approach.
Switching the nodeset to newer OS will be handled in a separate step
[1] http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-10-02-16.00.html
Co-Authored-By: Nate Johnston <nate.johnston@redhat.com>
Change-Id: I37c1cb42b3a94532e7b7fea21a929a39fe63f00b
In patch [1] timeout for
- tempest-full
- tempest-full-py3
was increaced to 3h.
Unfortunatelly it was done only for check queue.
I forgot to do the same change for jobs in gate queue
This patch adds same change for gate queue.
[1] https://review.openstack.org/#/c/614423/
Change-Id: I263124aa732efea8295313aeff7697b91c00f3f4
For jobs:
- tempest-full
- tempest-full-py3
Sometimes we hit timeouts which aren't related
directly to Neutron.
So, as was done for some other jobs in [1] it will also
increase timeout for tempest-full jobs.
This patch adds also our own list of irrelevant files for
tempest-full-py3 job as it wasn't specified before.
[1] https://review.openstack.org/#/c/613234/
Change-Id: I6e56b5f9243cdc29e8a36399ae98f95173e61c98
This reverts commit 0014c0c3734e8d344e4a45e127fbd0c86dcfaf3c.
This is handled generically now with this change and its dependency:
https://review.openstack.org/#/c/606853/
Change-Id: I360211cf60afb5611fb9e77fe6332fa59159708f
For jobs like:
- neutron-tempest-iptables_hybrid
- neutron-tempest-linuxbridge
- neutron-tempest-dvr
Sometimes we hit timeouts which aren't related
directly to Neutron.
As was decided on Neutron CI meeting [1], lets try
to increase jobs' timeout to 3h and check if that
will help to stabilize those jobs.
[1] http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-10-23-16.00.log.html#l-121
Change-Id: I24d694ba57aa3ff49f8c118486265925f1b4a611
The legacy job legacy-tempest-dsvm-neutron-pg-full is now named
tempest-pg-full - using the new tempest and Zuul v3 frameworks.
Change experimental job to use new job.
Change-Id: I40c93dbb863497173b097ba9112cbaf107d8232c
Depends-On: https://review.openstack.org/609530