The nova-tox-functional-py36 job was replaced with the current py38
version during Victoria by I1d6a2986fcb0435cfabdd104d202b65329909d2b.
However as clearly stated in both the Victoria and Xena runtime
reference documents python 3.6 remains supported through CentOS 8 and
later CentOS 8 stream.
This change reintroduces functional test coverage for py36 using a
CentOS 8 stream based job.
[1] https://governance.openstack.org/tc/reference/runtimes/victoria.html
[2] https://governance.openstack.org/tc/reference/runtimes/xena.html
Change-Id: I6ef77bd92f2595016a99d1953414d3f554f6b2eb
This currently runs in the 'check' pipeline, as part of the pep8 job,
which causes otherwise perfectly valid backports to report as failing
CI. There's no reason a stable core shouldn't be encouraged to review
these patches: we simply want to prevent them *merging* before their
parent(s). Resolve this conflict by moving the check to separate voting
job in the 'gate' pipeline as well as a non-voting job in the 'check'
pipeline to catch more obvious issues.
Change-Id: Id3e4452883f6a3cf44ff58b39ded82e882e28c23
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Bug #1931702 details soft lockups reported within the guest OS during
live migration with block migration and a volume attached. These lockups
then causing the request to detach the volume as part of the cleanup to
fail. For the time being we should skip these tests until the underlying
issue is resolved.
Related-Bug: #1931702
Change-Id: I7c1a647fb840fce98672a8429d554dd399cd13b7
The volume update or swap_volume API has long been a source of gate
failures within Nova. Most recently we've seen increased instability
when running the temptest.api.compute.admin.test_volume_swap tests as
part of the nova-next job as documented in bug #1929710.
This change temporarily removes the failing test from the nova-next job
while the underlying issue is identified lower in the virt stack.
Change-Id: Ib56a034fb08e309981d0b4553b8cee8d16b10152
Related-Bug: #1929710
This is no longer used with the removal of the legacy
nova-grenade-multinode job in I02b2b851a74f24816d2f782a66d94de81ee527b0.
dsvm-irrelevant-files is also renamed to nova-base-irrelevant-files and
now defined within the nova-live-migration job.
Change-Id: I67faa85618e2de1400d868299426b0ba8274c90e
If2608406776e0d5a06b726e65b55881e70562d18 dropped the single node
grenade job from the integrated-gate-compute template as it duplicates
the existing grenade-multinode job. However it doesn't remove the
remianing single node grenade job still present in the Nova project.
This change replaces the dsvm based nova-grenade-multinode job with the
zuulv3 native grenade-multinode based job.
Various legacy playbooks and hook scripts are also removed as they are
no longer used. Note that this does result in a loss of coverage for
ceph that should be replaced as soon as a zuulv3 native ceph based
multinode job is available.
Change-Id: I02b2b851a74f24816d2f782a66d94de81ee527b0
This patch explicitly enable ML2/OVS for the nova-next job.
Devstack is changing the Neutron default to OVN backend. Currently, the
nova-next job requires QoS minimum bandwidth support in its
post_test_hook.sh script [0] which is currently not supported in OVN [1]
(feature needs to come to core OVN first).
[0]
ede0147abd/gate/post_test_hook.sh (L131-L136)
[1] https://docs.openstack.org/neutron/latest/ovn/gaps.html
Change-Id: I91b8056e73658fc815eb2f6711e89d4ab5deed92
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
Tempest replaced the below rolevar for run-tempest role
- tempest_test_blacklist is replaced by tempest_test_exclude_list
- tempest_black_regex is replaced by tempest_exclude_regex
old name are still supported for compatiblity but we recommend
to switch to new one.
Change-Id: I4f2d01a4cf443f9c539158e77032cd3d8ce24ad7
Since Ib342e2d3c395830b4667a60de7e492d3b9de2f0a the nova gate has lacked
any libvirt live migration test coverage for ceph. This change
reintroduces this via a new zuulv3 native multinode live migration job
for ceph that includes additional instance evacuation coverage.
Depends-On: https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/711625
Change-Id: I6d0dbdcc84fe070e84d19d0c3d4306e6e0326e46
With the introduction of the libvirt-default-machine-type blueprint
operators are now able to change the default machine type used by an
existing environment more easily. This should hopefully allow more
deployments to switch to the modern q35 machine type, away from the
legacy pc machine type that is currently the default.
With this in mind this change aims to start testing the q35 machine type
as part of the nova-next job before we eventually change the default in
the future.
The following changes are made to the job to allow it to pass with q35:
- [libvirt]num_pcie_ports is increased to 24
This is required as more devices are now connected by default over PCIe.
- [compute-feature-enabled]ide_bus is disabled
The q35 machine type does not support an IDE bus so any tests using this
bus are now skipped.
Depends-On: https://review.opendev.org/c/openstack/devstack/+/779179
Depends-On: https://review.opendev.org/c/openstack/tempest/+/775630
blueprint: libvirt-default-machine-type
Change-Id: Iad1adbc23b31dd54a96299e7a8a4b622c15eed8d
As covered in the removed TODO this was to be done after bug #1771700
was resolved in Queens but instability in the job over the years stopped
this from ever happening.
With I7ad1d9820c48644bff7834560cdc7d5c13f7ed41 hopefully addressing the
only outstanding stability issue we can now finally mark the job as
voting again.
Related-Bug: #1771700
Change-Id: Ie9cba36ab602ab7c20c9a2c3b60e11e8506581ce
This is required as instance snapshots taken in this environment are
fully allocated RAW snapshots and consume considerably more space than
sparsely allocated RAW snapshots taken when Nova is using a file based
imagebackend.
We could look into sparsifying the resulting snapshots from the lvm
imagebackend but for the time being given the available space in our CI
hosts we can just extend space available to g-api via swift.
Closes-Bug: #1913451
Change-Id: I7ad1d9820c48644bff7834560cdc7d5c13f7ed41
As with the already listed encrypted volume tests this job specifically
blocks us from downloading non-raw images via Glance as part of these
tests so skip it.
Change-Id: Iaf6f6e0dbcb25561bf00e969e1964cd30e974e64
Closes-Bug: #1912607
This job tests the recently introduced direct download of rbd hosted
Glance images into a file based imagecache.
Depends-On: https://review.opendev.org/748212
Change-Id: I0933447e6caa0013f0b26dbf6532ff1976197e80
This patch adds both a tox target and a zuul job to run functional tests
with python3.9
Depends-On: https://review.opendev.org/760932
Change-Id: I672904e9bfb45a66a82331063c7d49c4bc0439df
This was incorrectly removed by
Ib342e2d3c395830b4667a60de7e492d3b9de2f0a while still being used by the
nova-grenade-multinode job. This was missed as the check queue appears
to default to silently skipping jobs where it can't find the parent
instead of failing.
Change-Id: I3ece71ab75a28a0ba662c56fb140525e8ce4aa6c
This change removes the original nova-live-migration job and replaces it
directly with the new Focal based zuulv3 native job.
The nova-dsvm-multinode-base base job is no longer used and so also
removed as part of this change.
Note that this new nova-live-migration job does not yet contain any
ceph coverage like the original, this is still pending and will be
completed early in the W cycle.
This change is being merged ahead of this to resolve bug #1901739, a
known QEMU -drive issue caused by the previous jobs use of libvirt 5.4.0
as provided by Ubuntu Bionic. The fix here being the migration to Ubuntu
Focal based jobs and libvirt 6.0.0 that now defaults to using QEMU
-blockdev.
Closes-Bug: #1901739
Change-Id: Ib342e2d3c395830b4667a60de7e492d3b9de2f0a
Both jobs deploy a multinode env before running their tests so just
append the new nova-evacuate tests to the end of the job.
Change-Id: If64cdf1002eec1504fa76eb4df39b6b2e4ff3728
This change reworks the evacuation parts of the original
nova-live-migration job into a zuulv3 native ansible role and initial
job covering local ephemeral and iSCSI/LVM volume attached instance
evacuation. Future jobs will cover ceph and other storage backends.
Change-Id: I380e9ca1e6a84da2b2ae577fb48781bf5c740e23
nova-ceph-multistore and neutron-tempest-linuxbridge
jobs are voting jobs but only run in check pipeline.
We should run all voting job in check as well as in gate
pipeline.
Change-Id: If6758c83a6bd95aefb7703529cbccd14e3adfee2
The old job name is still available as an alias for a while,
but it is time to switch away from it.
Change-Id: I93c35b386e1b1cbcff74fe0a2388f0eda5dea3b9
This initial change introduces a non-voiting
nova-multinode-live-migration check job. This initial job simply runs
the live migration tests against a multinode env.
Future changes will introduce ceph based live migration and evacuation
jobs before removing the original nova-live-migration job.
Change-Id: Ibbb3930a6e629e93a424b3ae048f599f11923be3
This makes our ceph job configure glance with multiple stores enabled.
It also makes sure that devstack uploads the cirros image to the file-
backed store, and configures nova for automatic copy-to-store
functionality. In order to allow this, we must grant all users ability
to copy-to-store for public images, since the tempest tests run as
their own users. This broadens the coverage of our ceph job to hit not
only the ceph paths, but the copy-to-store paths, as well as glance's
multi-store paths, and glance's async task paths.
Related to bp/rbd-glance-multistore
Depends-On: https://review.opendev.org/#/c/740322
Depends-On: https://review.opendev.org/#/c/738703
Change-Id: Iff5e9eaed7eb2345eaafc90c8cd6466a2cbca08c
The job was part of the neutron experimental queue but then removed
during the ussuri lifecycle.
See https://review.opendev.org/#/c/693630/
Change-Id: I04717b95dd44ae89f24bd74525d1c9607e3bc0fc
As per Victoria testing runtime[1], we need to tests py3.6,
py3.7, and py3.8.
- py3.7 is being tested with integration jobs.
- py3.6 and py3.8 are tested with unit test jobs.
Nova functional tests are testing py3.6 which can be moved to the latest
python available in this cycle which is 3.8. We do not need to run functional
or integration tests on each supported python version. Testing them on
the latest python version is enough. Coverage of all supported python version
is achieved via unit tests job.
[1] https://governance.openstack.org/tc/reference/runtimes/victoria.html
Change-Id: I1d6a2986fcb0435cfabdd104d202b65329909d2b
This change switches the single node legacy grenade-py3 job over to the
newly introduced Zuulv3 based grenade job.
Change-Id: I212692905a1d645cd911c2a161c13c794c0e0f4d