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
We're migrating now to openSUSE 15.0 (yes, 15.0 is newer than 42.3),
remove legacy job and replace with native Zuul v3 job running python3.
Change-Id: I40ac09e26deff2043aa2a903ac858685c4257318
Depends-On: https://review.openstack.org/609359
This job was set to be non-voting and was removed from
gate queue in [1]
It looks that patch [2] which was merged to stable/rocky
recently fixed this issue and this job is working fine again,
so lets make it voting and gating again.
[1] https://review.openstack.org/#/c/602097/
[2] https://review.openstack.org/#/c/595490/
Change-Id: Ied3b7c439056134388b16742448cd1da7ece04cf
Related-Bug: #1791989
In order to get openstack/placement installed as part of the
neutron grenade jobs, we have to list it as a required project.
Needed by https://review.openstack.org/604454/
Change-Id: I742660f398b52c62503acf00aaf7faa9a5a8650a
Use openstack-tox-cover template, this runs the cover job
in the check queue only.
Use openstack-lower-constraints-jobs template.
Remove jobs that are part of the templates.
Change-Id: Ieada5c2ee82497f4d6f07338df4577398d044fb6
This job is defined in Tempest to replace
neutron-tempest-multinode-full which was job defined
in Neutron's repo.
This job is set as non-voting in Neutron because old
neutron-tempest-multinode-full job was non-voting also.
If stability of this new job will be fine for us, we
can switch it to voting later.
Depends-On: https://review.openstack.org/#/c/598610/
Change-Id: I2dcbf4ade83760797b4e5072f0e05dac877842c9
When eventlet was bumped up to 0.24.1 in upper-constraints [1]
it started generating a pylint warning, since neutron has
support for older versions such as 0.22.0 that take a different
number of arguments. Just silence the warning.
Also, in order to get this through the gate, the
neutron-grenade-dvr-multinode check job is being temporarily
set to non-voting and removed from the gate. That change
should be reverted as soon as we fix bug 1791989.
[1] https://review.openstack.org/#/c/589382/
Change-Id: I169ecb6f33b670c5469919214a32645cd9eda206
Closes-Bug: #1791178
Related-Bug: #1791989
The autogenerated changes for the python3-first project duplicate
tempest-irrelevant-files, which was previously consolidated in [1].
This reconsolidates them.
[1] https://review.openstack.org/591524
Change-Id: I79b5f0745919f07118cbcdc08e79f971676a9e31
This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs as part of the
python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: Id22b50eb0ccd50f252313a01903f73a76ab97012
Story: #2002586
Task: #24314
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I03b604c04299bb9504739d41110c915c119ea809
Story: #2002586
Task: #24314
This patch adds exprimental tempest, functional and fullstack
jobs when neutron-api is served by a webserver as a part of
community goal.
Change-Id: Id88ca1a6997d39bf0d14589c0a2725b4ac109cec
The neutron-fullstack-python35 job, which is an integral part of the
python 3 community goal, is stable now. This change moves it from the
experimental queue to the check queue, but leaves it non-voting. Once
the Rocky release happens, we can use the additional data provided by
the extra runs and assess if it can be made voting.
Change-Id: I512094705ecbe1e470a623ada7e01c634a6d07be
In commit [1] openvswitch firewall driver is switched to be
default one used in devstack.
So various tempest jobs will use this driver and it will be
tested.
We now need separate job to test non-default firewall driver
which currently is iptables-hybrid driver.
[1] https://review.openstack.org/#/c/568297/
Depends-On: https://review.openstack.org/#/c/568297/
Change-Id: I6061a173c95c8a41a61bfa298ae5964cc9b5d2e8
Rally team finally added native Zuul V3 jobs (with a bunch of separate
roles and etc) and for simplification of maintainance, it would be nice
to use them.
Change-Id: I755e776a7c24e1bcdf144d7af071a52633aeb94d
As part of community goal to have services working with Python 3.5, this
patch adds back the exeperimental Python 3.5 functional and fullstack jobs
that got lost somewhere during zuul v3 migration.
Change-Id: I24506b94f3f4e111b3968e57deb683e9c874941c
This job works as voting in check queue since [1]
was merged.
It works without problems for few weeks so now it's
time to add it to gate queue also.
[1] https://review.openstack.org/#/c/560097/
Change-Id: I051da2af89cee53db84fd7a4df458e7abbfddaa7
We in openstack-infra would like to remove these nodesets, our new
ones will provide the same functionality.
Change-Id: I5bd3f26f1624491bb3f211e2d777f29bdf7c0a37
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
It's been tracked for a while and considered stable as per Grafana
dashboard its failure rate is along with other tempest jobs. This patch
makes the job voting in the check queue and not putting to gate queue on
purpose.
Change-Id: I18101cdb864ea28f711d225f74d607d70548a129
Fullstack job's failure rate is reasonable since few weeks,
job is already working as "voting" and there is no problem
with that.
Because of that it is now added also to gate queue.
Change-Id: I346c3c97b26932e2f02893cf5f3b63090cd81ee0
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: I78f0beea8f78aa635b59bc80c97fec41412049e0
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
As failure rate for fullstack job in check queue is
low we decided to make fullstack job voting in
check queue.
If it will work fine in check queue we will set it
to be running also in gate queue.
Change-Id: I97c602670fc4f50e156066c61b30874f76cadcf8
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Ia190b510f06d1140f95589543596d9949cfc4f88
We already have tempest-full job that is identical and defined elsewhere
(in tempest repo) that is part of our queues.
Change-Id: I788973513ec17bcc0df362dd42783dcc7aa8e452
This references the template defined in the neutron-tempest-plugin repo
in order to run the jobs defined there.
Change-Id: I5044db2c80b77ed0e01201216a4be05b4ea67cd7
Depends-On: I98c42a407e15e9db016103bd0b5484ad7f12649d
* https://review.openstack.org/520370 moves the zuulv3 neutron
tempest plugin jobs to neutron-tempest-plugin as those jobs
are meant for testing neutron tempest tests. If we donot move
the jobs there we cannot inherit the same job to neutron project.
Depends-On: I950913a2d76d1fd75dbf535c59c7879e5a93c092
Needed-By: I98c42a407e15e9db016103bd0b5484ad7f12649d
Change-Id: Ic4e88f1f9d2ea7803efe8d0e32117df304d6d3e5
The other devstack jobs in project-config all have a releasenotes
exclusion on them. Add one to these too.
Change-Id: I60173e21d5ff514f15573ccb9f535f04d130fe42
* In order to test the tempest plugin, this patch adds following
jobs against neutron repo.
- neutron-tempest-plugin-api for api tests
- neutron-tempest-plugin-dvr-multinode-scenario and
neutron-tempest-plugin-scenario-linuxbridge for scenario tests
Depends-On: I42d389836e72813fdeebc797a577f4a8ac2ee603
Change-Id: Iab7f7bcec9597444041c6d6891b5e0d9a03ba039