tempest-full-py3 job runs on nova check and gate pipeline
as part of 'integrated-gate-py35' template.
Unlike tempest-full or other job, nova job definition list on
project-config side[1] does not define the irrelevant-files for
tempest-full-py job which leads to run this job on doc/test file
only change also.
This commit defines the irrelevant-files for tempest-full-py3 on
nova's zuul.yaml.
Closes-Bug: #1785425
[1] 57907fbf04/zuul.d/projects.yaml (L9283)
Change-Id: I887177c078a53c53e84289a6b134d7ea357dfbef
change https://review.openstack.org/559401 moved
legacy-tempest-dsvm-nova-os-vif to os-vif repo and renamed it to
os-vif-ovs. Move the job from project-config set up to nova, it was
in experimental queue there.
Needed-By: https://review.openstack.org/583024
Change-Id: I86a9863fe3a6a9e132bf451d57349c08e4328ed4
We can define common variables for irrelevant-files
used across various dsvm and functional jobs and then
reference them using node anchors to avoid duplication.
Change-Id: Ife046b91c96dd300e8c46125b75623d8e12b8da3
Co-Authored-By: Stephen Finucane <stephenfin@redhat.com>
ironic-tempest-dsvm-ipa-wholedisk-bios-agent_ipmitool-tinyipa is
defined in the ironic repo but nova uses it because it's defined
in the project-config repo with it's own irrelevant-files list.
Due to a recent change in zuul [1], the definition from project-config
overrides the irrelevant-files from the job definition in ironic and
results in us running this job on things like docs-only changes in
nova, which is not awesome.
This change moves the job usage in-tree from project-config and updates
the irrelevant-files list to match nova-dsvm-base.
Since project-config is branchless, we'll have to backport this in-tree
change to nova's stable branches to continue running this job on nova
stable branches once the override is removed from project-config.
[1] http://lists.openstack.org/pipermail/openstack-dev/2018-June/131304.html
Change-Id: I9435fe84c8dc8a6f35ffb195ddbf71ca34edb242
Closes-Bug: #1776981
This changes the nova-lvm job to run in the check queue on libvirt
driver changes only, and only runs the tempest compute API tests
to save time since we don't need to run things like the cinder,
glance, neutron etc API tests.
Once we're comfortable with the stability of this job we can
make it voting and gating.
This is in response to bug 1771700 which could have been prevented
if we were gating on the nova-lvm job on libvirt changes.
Change-Id: Ieaf00bcb6cb885e544d05b6f7276b6470b123258
Related-Bug: #1771700
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: Ic28558ee6481d49a9b4e5dc2c4182504e330448f
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Co-Authored-by: Eric Fried <efried@us.ibm.com>
Co-Authored-by: Jim Rollenhagen <jim@jimrollenhagen.com>
The nova-live-migration test hook configuration is in
nova/tests/live_migration/hooks and because of the
irrelevant-files list on the job, changes to those
setup scripts are not self-testing. This change fixes
the regex so we can self-test the nova-live-migration
job changes.
Change-Id: Ia7e35d483f660e98eea5e109e010f77d5419af85
This defines the nova-live-migration job, based on the
tempest-dsvm-multinode-live-migration job from openstack-zuul-jobs.
The branch override parts of the job definition are removed since
the job will be defined per-branch now.
Change-Id: Idea86d6bb648b1e6fef8813dbe569724ce81a750
The dependent change to devstack makes devstack use the
Queens Ubuntu Cloud Archive which has libvirt 4.0.0 so we
can remove the flag from the job which disabled the UCA
in devstack since the versions of qemu and libvirt in the
Pike UCA wouldn't work for multiattach.
This also allows us to make the job voting and gating again.
Closes-Bug: #1763382
Depends-On: https://review.openstack.org/554314
Depends-On: https://review.openstack.org/560931
Change-Id: I0962474ff6dfc5fa97670c09a1af97a0f34cd54f
For in-tree job definitions, the job is branch-specific
by design, so we don't need the stable branch exclusion
specifier as it won't run on those branches anyway since
it's not defined for those branches.
Related to https://storyboard.openstack.org/#!/story/2001839
Related-Bug: #1763382
Change-Id: I78dead482e2ed8262745cb08c9f4ab71035adb33
Since Icb971831c8d4fe5f940d9e7993d53f1c3765e30f merged
in devstack to use the Queens UCA, the nova-multiattach
job has been failing to start nova-compute due to permission
errors connecting to libvirt, which probably has something
to do with the stack user not having access to the proper
libvirt(d) group.
It's weird since this was working in change
I0962474ff6dfc5fa97670c09a1af97a0f34cd54f to make the
nova-multiattach job use the Queens UCA.
Anyway, let's make it non-voting to stop the bleeding while
we can figure out the actual problem.
Change-Id: I3911c902cecfa8e66fccffd9fe0e4f462eacd588
Related-Bug: #1763382
This defines the nova-cells-v1 job, based the tempest-dsvm-cells
job from openstack-zuul-jobs.
The branch override parts of the job definition are removed since
the job will be defined per-branch now (we'll also have to backport
this to stable/queens).
There will be related changes to project-config, devstack, tempest
and openstack-zuul-jobs on this topic branch to use the new job name.
Part of blueprint remove-nova-network
Change-Id: I25c87f27c69e0cdb74e8553305a09cb85f43d87e
Bug 1747511 was fixed with change
I363182e916480c734cc37f279e8e89c8f3ec653c in Queens
so we can make the nova-next job voting now.
We want this job voting and gating since it tests
some things not found in other job configurations,
like TLS proxy, service user tokens, and post-test hooks
for nova-manage commands like archive_deleted_rows.
Change-Id: I4cfc3b100f8829deb97e491f40a3020b3c8eb026
Related-Bug: #1747511
This adds an experimental queue job to run non-slow tempest
API and scenario tests using the CachingScheduler as the
scheduler driver.
A blacklist is added since there are a few tests that rely on
filters which don't work well with the CachingScheduler.
The CachingScheduler is deprecated, but this is useful to have
when we're making changes to the scheduler or flows within the
code that involve the scheduler, such as the alternate hosts
work.
Change-Id: I8630ea11c3067ed934de2ef27a63432418e98c33
This moves the legacy-tempest-dsvm-neutron-nova-next-full
job from openstack-zuul-jobs in-tree and updates a
few things since it's now branch specific:
- The cells v2 and placement stuff can be removed since those
are required now (they were optional when this job would run
against newton changes).
- Use nova/gate/post_test_hook.sh rather than the symlink under
nova/tools/hooks/.
The job is currently non-voting and needs to remain that way
until bug 1747511 is fixed.
According to the branch restrictions in project-config, apparently
this job is only running against stable/newton (which no longer
exists) and master, presumably when master was pike. We should also
run this job against stable/pike for the service user test coverage
and post_test_hook.sh run, so we'll likely backport this change
to stable/pike as well.
The related project-config change is:
I36d96f89b3e5323746fcbcef5cc7e4d0384a184d
Change-Id: I24a5f73c29094a23e2fdef8ee8b43601300af593
- renames the base job that is for dsvm jobs
- removes the unused legacy branch override stuff
- moves the comment about keeping the jobs sorted
Change-Id: Idf20864fe3371e4bbafb8c18bcf979a8f3c3eb62
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I27533519a8d77bae6fb58b61bf41daf5fca50d3c
This change adds a new voting check/gate queue job for running
volume multiattach compute API tests.
This configures devstack to enable tempest for volume multiattach
support and disables the Pike UCA since we need qemu<2.10 for
libvirt to work with multiattach volumes.
Depends on the following devstack patch to add the
ENABLE_VOLUME_MULTIATTACH variable. The devstack patch
depends on the tempest patch that adds the volume multiattach
tests and the tempest patch depends on the series of nova
changes that add volume multiattach support.
Depends-On: I46b7eabf6a28f230666f6933a087f73cb4408348
Depends on the following nova patch to fix a bug when
creating a server snapshot of a paused instance when not
using the Pike UCA:
Depends-On: If6c4dd6890ad6e2d00b186c6a9aa85f507b354e0
Depends on the tip of the series of Tempest tests which include
additional tests for resize with a multiattach volume and swap
volume with a multiattach volume.
Depends-On: I751e9e4237e2997e102dd13c4f060deaea73d543
Part of blueprint multi-attach-volume
Change-Id: I51adbbdf13711e463b4d25c2ffd4a3123cd65675
Recently we saw frequent job timeouts probably due to the intel kernel
patches. So this patch bumps the functional and functional-py35 jobs
timeout from 1800 seconds to 3600 seconds.
Change-Id: I632e006e1ba62c998955a04421e0e0c6311544cb
Closes-Bug: #1745398
To be able to define different irrelevant-files for the functional jobs
than the ones defined in openstack-zuul-jobs we need to copy the jobs to
the nova tree and modify the fields in tree.
Technically we could factor out the irrelevant-files regexp list from
functional and functional-py35 jobs as they are the same today. However
in the future when they diverge we cannot simply override the
irrelevant-files in one of the jobs. Therefore this patch does not
introduce a common base job for functinal and functional-py35 jobs
to discurage trying to override.
The openstack-tox-functional and fuctional-py35 are removed from the
nova part of the project-config in
I56d44f8dff41dbf3b2ff2382fa39b364f55f9a44
Closes-Bug: #1742962
Change-Id: Ia684786d1622da7af31aa4479fc883a7c65848ff
Implement part of step one of the zuulv3 migration guide: move the
purely nova projects to the nova repo [1]. This does not migrate any
jobs used in other projects nor does it convert what is migrated to use
the new 'devstack' or 'devstack-tempest' base jobs. Both of these steps
should be done separately.
What's migrated:
- experimental:
- legacy-tempest-dsvm-nova-lvm (renamed to nova-lvm)
What's dropped:
- experimental:
- legacy-tempest-dsvm-nova-lxc (no one's using this)
- legacy-tempest-dsvm-nova-wsgi-full (WSGI is the default since Pike)
What's still to be migrated, here or to other projects:
- check:
- legacy-grenade-dsvm-neutron-multinode
- legacy-grenade-dsvm-neutron-multinode-live-migration
- legacy-tempest-dsvm-cells
- legacy-tempest-dsvm-full-devstack-plugin-ceph
- legacy-tempest-dsvm-neutron-linuxbridge
- legacy-tempest-dsvm-neutron-multinode-full
- legacy-tempest-dsvm-neutron-nova-next-full
- legacy-tempest-dsvm-multinode-live-migration
- ironic-tempest-dsvm-ipa-wholedisk-bios-agent_ipmitool-tinyipa
- legacy-tempest-dsvm-neutron-full
- legacy-grenade-dsvm-neutron
- gate:
- legacy-tempest-dsvm-cells
- legacy-tempest-dsvm-multinode-live-migration
- legacy-tempest-dsvm-neutron-full
- legacy-grenade-dsvm-neutron
- experimental:
- legacy-tempest-dsvm-nova-v20-api
- legacy-grenade-dsvm-neutron-nova-next
- legacy-tempest-dsvm-multinode-full
- legacy-tempest-dsvm-neutron-dvr-multinode-full
- legacy-tempest-dsvm-neutron-dvr-ha-multinode-full
- legacy-tempest-dsvm-neutron-scenario-multinode-lvm-multibackend
- ironic-tempest-dsvm-pxe_ipa-full
- legacy-tempest-dsvm-nova-os-vif
- legacy-tempest-dsvm-nova-libvirt-kvm-apr
- legacy-grenade-dsvm-neutron-multinode-zero-downtime
- ironic-tempest-dsvm-multitenant-network
- ironic-tempest-dsvm-ipa-resourceclasses-partition-pxe_ipmitool-tinyipa
- legacy-tempest-dsvm-full-devstack-plugin-nfs
- legacy-tripleo-ci-centos-7-nonha-multinode-oooq
- legacy-barbican-simple-crypto-dsvm-tempest-nova
- legacy-tempest-dsvm-py35-full-devstack-plugin-ceph
- legacy-tempest-dsvm-neutron-pg-full
- legacy-tempest-dsvm-neutron-full-opensuse-423
- legacy-tempest-dsvm-neutron-src-oslo.versionedobjects
[1] https://docs.openstack.org/infra/manual/zuulv3.html#legacy-job-migration-details
Change-Id: I41b03a34795efe139d5911c605cdbd3c47a2f059
