Looking at a recent timeout at [1], the linuxbridge job was a few
tests away from completing when the job timed out. The root cause
of the timeout was actually devstack-gate-setup-workspace-new taking
22 minutes instead of the 3-5 it should have which ate up a significant
amount of time.
I analyzed the difference between the execution time of the actual test
suite run and the a test suite run on the OVS job and it took about 5
minutes longer.
Adding 10 minutes should be enough to compensate for landing on a slow
node with a long setup time and should bring timeouts to parity with the
OVS job.
1. http://logs.openstack.org/75/502975/1/gate/
gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial/13d6c14/
Change-Id: Ieededb459e884e2a158678da7b024549423a76b1
Related-Bug: #1660612
As the comment says: These can be removed once mitaka is eol'ed - these
are indeed not used after all the cleanups. Remove them.
Change-Id: Ie0d2625a61fef51a9730c5770286903f05bc5e21
Remove special treatment for mitaka in jobs where the repo has now
the stable/mitaka branch retired.
Change-Id: I1af11cf22c145bb96e93485460cca277287c88ca
Gate hook sets up configuration for rootwrap which depends on VENV. In
case of python3 job flavor, rootwrap is configured to wrong venv and
rootwrap doesn't work in tests.
Change-Id: I49b66d6151efab2f1ecea35b0dc72ae02c9c02f8
Depends-On: I7fea6e9aa09550e00edf6ce2d7301312307df5fd
We want to run dstat during test runs [1], and unstacking just kills the
service.
[1] I73857f63f512e26d595c61a20ec5bf22d2fb0da7
Change-Id: I7916c629f267de88725284f2cfc696c22e88d150
We plan to use devstack-gate for the job (to inherit its setting
required for successful gate pass, like IPV4_ADDRS_SAFE_TO_USE). This
override makes it so that devstack-gate is not cloned, and hence an
attempt to trigger gate.sh script fails.
An alternative would be to add devstack-gate to the list, but Clark
Boylan told me we slowly move to removing all those overrides and just
trimming the default list of cloned projects, so it seems better to
align with infra ways, especially since we were bitten by the override
already.
Partial-Bug: #1693689
Needed-By: Iee7cc4c129e6e9eab91107fda92f66c5379d6f95
Change-Id: Ic874a08ce41dbfb2c7e43f61c92f1c7f13de16ea
The AMQP 1.0 devstack plugin support a couple of different message bus
configurations. This patch adds support for these additional
configurations to the dsvm-full and tempest-neutron-dsvm
oslo.messaging tests.
This patch also removes all the oslo.messaging mitaka/trusty tests as
mitaka is EOL.
Change-Id: Iccc60b634b81b9761c0ec564c5aa263582f13ebf
Change Id2caf9561b361c1d4950856423282535d067e015 for devstack adds all
repositories in DEVSTACK_PROJECT_FROM_GIT to PROJECTS, so no need to add
repos in jobs to PROJECTS if there are in DEVSTACK_PROJECT_FROM_GIT.
This change went through all of jenkins/jobs and removed PROJECTS where
there is direct 1:1 correspondence. For a few files, especially ironic
and freezer, this was not doable.
Change-Id: I4b51e33b9bc0f1cb7948b69abf104e0b57b9ff52
ryu is often released(basically every month). And the new release
may affect the behavior of ovs agent. This adds job to check neutron
with the ryu master to avoid a trouble with the new ryu release.
It is added as an experimental job firstly and if it is stable
we make it a periodic job.
Change-Id: I82f404a04a1082140208546fad28ca369d210d5a
In [1] the VNC related errors for
gate-tempest-dsvm-multinode-full-ubuntu-xenial-nv were fixed, but we are
still seeing them in
gate-tempest-dsvm-neutron-dvr-*multinode-full-ubuntu-xenial-nv jobs, so
add the same local_conf settings there.
[1] https://review.openstack.org/444164
Change-Id: I9d78e7f96af09a1983b90eb5f7fa721d42c3605b
This is needed so that we can choose a custom firewall driver (ovsfw)
for openvswitch job flavour. This is needed because one of tests target
connectivity for trunk ports, and this works only when using the new
ovsfw driver.
The gate hook already matches the argument against 'dsvm-scenario'
pattern and doesn't require equality, so this change should not break
existing jobs.
This change relies on I5a36fa3a44e9de4225a00c854a95ad7b5d8987f7.
Depends-On: I5a36fa3a44e9de4225a00c854a95ad7b5d8987f7
Change-Id: Ie3261f528ccedb5fc2b1597c84cf998e82ede2cd
The trove repo now uses tools/test-setup.sh we do not need the db jobs
anymore, change to the standard python unit jobs.
Also use standard pylint job-template which does the same as the tox
template.
Remove all templates and job-groups for the db-jobs since it's last user
has been removed.
Only leave mysql setup jobs for bifrost in.
Change-Id: I92e6e6502c2c516babf2bf66f3514875f77c460e
Depends-On: I3463e75057d0d4544f6a0212da888759ab5e171b
This is one of the projects that used an inline pre_test_hook to set
local.conf. Move it over to the new stanza to test this all works. The
only use of this in the gate is non voting, so we should be able to
land and iterate to make sure that this is really working.
Change-Id: I64f610e963192be48166e8ef638fee85075dcae0
These tests use Ubuntu image for instances which makes it longer to
boot. On certain gate resources it takes sometimes longer than 6
minutes to succesfully start sshd on instances.
This patch sets the tempest concurrency run to 2 to avoid
overloading the environment.
Change-Id: I197ac2764cf9b87e0544b5655fb5db8a1dcba555
Linuxbridge so far does not support DVR. Use the new gate_hook 2nd
argument to disable tests for the feature.
Depends-On: I05233e69801be27cc35211148a53af02af29c8a5
Change-Id: I0e94c5d7f65bbb1d803df0d2f99389ae19556480
The project is moving into DVR+HA direction for all gate jobs. At this
point, adding jobs that are not DVR+HA is counterproductive.
Of course, since Linuxbridge does not work with DVR yet, we keep that
other scenario job flavour as-is. But there is no excuse to care about
that non-dvr OVS job.
Change-Id: I7b029acd19d8705882792a0aa6ae4aac68a4253e
Note: the job will pass the same first argument into the gate hook as
non-DVR job. We will use DEVSTACK_GATE_NEUTRON_DVR to distinguish the
flavour if needed.
Change-Id: I1fa3eaa3788a844f662adc98de1ec8d11f221d6b
Liberty is EOL, start cleaning up all of the special things we have in
place for handling libertyisms. Note that this doesn't touch the configs
for deployment projects as they may still attempt to support liberty via
distro packages.
Change-Id: I7faa16c1d6038204a4b42167ed91b73175abe58c
We have now some rather long job-template names, shorten them with
replacing job-suffix with suffix.
Before this change we had 1500 usages of job-suffix and 700 of just
suffix. This change therefore unifies to one setting.
Note that this does not change any job names at all, they are unchanged,
it changes and shortens only the names of job-templates.
Change-Id: I514df039a848d9f6619bca3adc05dfb84a761fc9
This moves the ipv6 related neutron jobs ahead to xenial as well as an
experimental pecan job.
In addition to this the configuration was modified to be simpler to read
(which aided in determining what work was leftover to Xenailify
neutron).
Change-Id: Ia4102a25dda79b2edad583867c929dcb7500a1b4
Convert further jobs to xenial so that stable/newton and newer runs on
xenial.
Node that the non-voting xenial job previously run on mitaka as well, I
removed it since a xenial job on mitaka does not make sense - there's no
trusty job added instead.
Change-Id: Ic1dd413f25bac74bb9eb24d65c075e6116a2c7df
Stop running these jobs on trusty as they are restricted to >= newton
already. Run them on Xenial as >= newton should run on Xenial.
Change-Id: I5ac6c2709dc15f36105bd3f0a1f14c860d04783e
Make these two jobs explicitly Trusty since they only run against
liberty and mitaka. We should consider just deleting them entirely since
they are non voting experimental jobs against older stable branches, eg
their situation is never going to change.
Change-Id: I070749d563652930c40a7058d4656917c9c5fc57
Adding a three node label to nodepool as we need a three node
setup to test DVR+HA with tempest.
Existing Devstack gate will set agent_mode to 'dvr' in both compute
nodes. So it is still a DVR only multinode setup with 3 nodes.
Change[1] in devstack gate submitted to change one compute node's
agent_mode to dvr_snat, to make it DVR+HA.
[1] https://review.openstack.org/#/c/383827/
Change-Id: I370643277a3b23e7f47e413cf880daa9af1eb831
Let the default branch regex apply for the jobs. Also, go
straight to xenial bypassing the non-voting purgatory as
there is nothing specific about the jobs that is affected
by the node switch.
Change-Id: Idea274792b6f38f4a43737910c6a0372834e8846
This enables TLS in the neutron linuxbridge, dvr, and non dvr multinode
jobs. They pass with tls-enabled, see
https://review.openstack.org/#/c/382564/ for the results.
Change-Id: I68aee8069919851a0d63fc4710ee2b4080e52fb8
Depends-On: I5f603b22c0e4f1e9c9a984c215680aec3a146703
* Use the '-nv' job suffix for non-voting job
* Enable gate-tempest-neutron test of AMQP 1.0 driver
* To run on mitaka, newton and master
Change-Id: I8f96e9ad51440ff014ed8375492c6b49b7cd22c7
Currently we don't have any job that triggers dvr multinode scenario
tests from Neutron tree. This patch adds introduces such a job for
Neutron experimental queue.
Change-Id: If5e3722c62b470c62b547444c9a1f5938f1c0667
Use xenial as node - and py35 as environment - for these jobs that run
on master. We have switched the py34 job already to py35 with xenial.
Update grafana for the change.
Update tox environment to use a variable.
Change-Id: Iadc4e03a4176a83e97c3b166c6043516ac57bcd8
The switch to xenial has revelead that hardcoding eth0 is
a bad idea and we should fall back to using the interface
for the default route [1].
[1] https://review.openstack.org/#/c/367699/
Depends-On: I7859437f97e6cab929e90208fe56f7efd62dfe01
Change-Id: Ib63268becee986a0a11e8ecbdb517b9d1e681583
This job isn't currently passing on xenial instances. Continue to run
the existing job on trusty for check and gate against all branches but
add a xenial job that can be run in experimental so that this can be
corrected.
Change-Id: I454b21ed81de57c392575e6a5b3cf731500c6138
Continue the trusty/xenial split by running the linuxbridge and dvr
neutron tempest jobs on xenial for branches >= newton. This has been
tested on xenial instances booted off of the infra images then running
the reproduce.sh scripst for each of these jobs on them. The
reproduce.sh scripts came from the gate jobs for change 358866. These
seem to run happily on xenial just like the normal tempest full job.
Change-Id: I0845b408bae6f463b957ac3bc705048ea4005fee
These jobs are part of experimental queue for now, until we are confident
enough to switch check queue for using Xenial as well.
Change-Id: Ice5a6561fe4fee9f98a6a92307f9392b37e28497
Some neutron stadium repos don't have a functional test job and
instead have their "models-migrations sync test" in the python
unit test job. This test requires mysql & postgresql DB backends.
Change-Id: I165fea6ac6ca16f23f74485a7f97d1526a56b036
Testing neutron-lib periodically with unit test jobs from Neutron stadium
projects can help prevent breakages detected at the time of a neutron-lib
release and it will speed development and maturity of the library.
This patch introduces the configuration necessary for running unit
tests against the master version of neutron-lib. The support is limited
to py34, as that would suffice to ensure coverage.
Change-Id: Ib1e4dbf92aab4ec09ad3ce54255ca729941784fa
The OVS native configuration is going to be on by default since
Newton. Add a reminder that at some point in the future it is ok
to drop job configurations and clean up the experimental pipeline.
Change-Id: Iaa98116b7c721c5c8ae83df8d6ac02445172a841
Depends-on: If3b27a623da762989980157a29376f8fa9bc991e
In order to consider switching to native interfaces to
OVS (i.e. using Ryu/OVS Python IDL libraries rather than
shelling out with rootwrap), we need to start watching
these jobs to see how they perform. Before doing that,
we need both native interfaces to be enabled.
Change-Id: I252902d0a0debe6fae4d023cd118ef20f15b47d9
Similarly to what was done in [1], this is about scenario tests.
The job did not take off in Mitaka, so add the release to the list of skipped branches.
Drop the s suffix for consistency.
[1] If5f7ea82c45494953452f728fabb7403d0b6e14e
Change-Id: I77827d2e6e07fbfb39727d823628094d730fcdd8
Neutron was amongst one of the earliest projects that promoted the
idea of colocating more advanced tests within the project's source
repo itself. The job gate-neutron-dsvm-api was created out of the
tempest backbone when no plugin/tempest-lib were a thing. Things
have matured since, therefore it is time to update some of the
plumbing underpinning this job so that we can start using some of
the latest cool stuff that Tempest has to offer.
The switch must be made conditional to branches since the it only
makes sense from Newton onward.
Depends-on: Ia233aa162746845f6ae08a8157dcd242dcd58eab
Change-Id: If5f7ea82c45494953452f728fabb7403d0b6e14e
This change moves the job definition closer to the other
job definitions available in the neutron.yaml file.
It also replaces the suffix with 'scenarios', which is more
intuitive than 'plus', and better reflects the nature of testing
that this job is going to carry out.
Finally, it adds a post hook, and tune some configuration knobs
to allow for finer control of its execution.
Change-Id: I24be6ddc14a40950bb9ffc2c91e6150a6a74d266
Monty Taylor