This reverts us back to using the standard disk image for most of our
tests, which is more representative of how people actually use nova.
This leaves the UEC image on a few jobs for the sake of comparison
data for the time being, and because we should actually test that
code path if we're going to say we support it.
Change-Id: I16ed92d342464325d4bef33c1e22b328bcfbe7d6
This uses the OCaaS feature in devstack which saves *minutes* of time
running devstack by effectively caching the openstackclient startup
instead of taking that hit for every invocation.
Change-Id: I78308128c6249f7f871e0231ce717b1ec0f88509
This change adds the
ironic-tempest-ipa-wholedisk-direct-tinyipa-multinode-shard
to the periodic-weekly and experimental pipelines replacing
the existing ironic-tempest-ipa-wholedisk-direct-tinyipa-multinode
job in the experimental line.
&policies-irrelevant-files is moved to the job defintions to
make workign on jobs simpler when commeting out jobs during devleopemt
yes this is unrelated but it make our lives simpler.
Change-Id: I1ee8f7f7d0cbcfb3a8cd61b5fec201b4ba4bf671
nova-lvm ocationally has OOM events causing
g-api to get killed. This can result in test failures
with a 502 form glance so we bump the swap to 8G
like the ceph jobs to avoid that.
Change-Id: Ib88f9feb692ee440b8f73e9b3dca56c08dadb665
This is another follow up for change
I1a6468fbfa51eedec0ab91d73f313784a9a618a0 which missed setting the
*uec_image_vars for jobs that are not defined in Nova. For example,
the tempest-integrated-compute job is not defined in Nova and if we
don't set *uec_image_vars for it, it will not use the UEC image and
will instead use the default full image.
This also sets *uec_image_vars for one job defined in Nova,
nova-osprofiler-redis, that was missed in the original change.
Change-Id: Ia8741d46c28277e9addadf0e2a568c3ad86fb8dc
This is a follow up for change
I1a6468fbfa51eedec0ab91d73f313784a9a618a0 which had residue from an
earlier PS that set DEFAULT_IMAGE_NAME and DEFAULT_IMAGE_FILE_NAME
intended to override project.vars. The project.vars approach did not
work because we needed to set IMAGE_URLS as well and the
devstack-tempest ancestor job sets IMAGE_URLS which overrides
project.vars.
The approach was changed to use YAML anchors instead of project.vars to
reduce duplication, which made the setting of DEFAULT_IMAGE_NAME and
DEFAULT_IMAGE_FILE_NAME in nova-next redundant as the default values
from Devstack can be used.
This removes the setting of DEFAULT_IMAGE_NAME and
DEFAULT_IMAGE_FILE_NAME in nova-next.
Change-Id: I3929b6c55d77575a6c0bd205f933cc2a690db91e
This change is being proposed in response to guest kernel panics that
are happening occasionally in the nova-next CI job. In these particular
cases, we see messages like the following in the guest console log dump
[1]:
pci 0000:00:03.6: BAR 13: no space for [io size 0x1000]
pci 0000:00:03.6: BAR 13: failed to assign [io size 0x1000]
which seems to indicate the guest is running out of memory to allocate
to the pcie devices.
This lowers num_pcie_ports to 12 from 24 in an effort to use less
memory.
[1] https://pastebin.com/raw/cVDem0Xr
Change-Id: Ibfa65a00dd91e6c3f28fef837a7e172221f72f42
Some of the object unit tests grub Mock object unintentionally, and
that results in failure during initializing an versioned object,
because the Mock object does not present its version correctly.
This fixes that problem
The sqlalchemy-2x job is made non-voting because this job requires
oslo.utils 6.3.0 which is blocked by this problem.
Closes-Bug: #2043116
Related-Bug: #2042886
Change-Id: Id1c1b77c020e2d8f0ac61c2aee86c9f37d388d53
We recently found a rolling-upgrade bug on rebuild so we need to make
sure that grenade-multinode can verify all our instance actions.
Given we pin the compute RPC API version to the N-1 compute one, we are
sure that all RPC calls continue to behave the previous release.
NOTE : Given the previous cycle was already supporting 6.2 RPC version,
we can't test here the previous problems hence why this is the last
patch from the series.
Change-Id: I1d8deb139922494dd74ff32965fd7dd74d1d768b
Related-Bug: #2040264
due to bug #1940425 where ml2/ovn is not correctly configuring the
active status on trunk port we see test_live_migration_with_trunk
fail more often then not.
This was previously disbaled in tempest and then fixed in neutorn.
the tempest skip was then reverted and so was the neutron fix as
it broke somethign else... so this is failing in our gate again.
This change skips test_live_migration_with_trunk on all jobs that
are using ml2/ovn but keeps it enabled on the hybrid plug job
which uses ml2/ovs.
Related-Bug: #1940425
Change-Id: I0a8dd6e6e30526aa2841b4db67ed9affed166fd8
modifies nova-ovs-hybrid-plug job to disable cinder and swift to
ensure we test for this going forward.
Change-Id: I52046e6f7acdfb20eeba67dda59cbb5169e5d17e
This job is marked as non-voting in the parent definition, which
causes us to run it in gate as non-voting, which is just a waste of
resources. Remove it from the gate queue until it is marked as voting
in the definition (or maybe consider just leaving it out).
Depends-On: https://review.opendev.org/c/openstack/devstack/+/890136
Change-Id: I2ddbafe851be2c7826d78613f12560a1713ac1b1
Qemu>=5.0.0 bumped the default tb-cache size to 1GiB(from 32MiB)
and this made it difficult to run multiple guest VMs on systems
running with lower memory. With Libvirt>=8.0.0 it's possible to
configure lower tb-cache size.
Below config option is introduced to allow configure
TB cache size as per environment needs, this only
applies to 'virt_type=qemu':-
[libvirt]tb_cache_size
Also enable this flag in nova-next job.
[1] https://github.com/qemu/qemu/commit/600e17b26
[2] https://gitlab.com/libvirt/libvirt/-/commit/58bf03f85
Closes-Bug: #1949606
Implements: blueprint libvirt-tb-cache-size
Change-Id: I49d2276ff3d3cc5d560a1bd96f13408e798b256a
As of I8ca059a4702471d4d30ea5a06079859eba3f5a81 validations
are now requried for test_rebuild_volume_backed_server.
Validations are also required for any volume attach/detach based test
in general due to know qemu issues.
This patch just turns them back on to unblock the gate.
Closes-Bug: #2025813
Change-Id: Ia198f712e2ad277743aed08e27e480208f463ac7
We are about to drop Fedora support as the latest image in upstream
has been transitioned to EOL. Centos 9 Stream has evolved as
replacement platform for new features. Patch which removes fedora
jobs and nodeset from devstack:
https://review.opendev.org/c/openstack/devstack/+/885467
Change-Id: Ib7d3dd93602c94fd801f8fe5daa26353b04f589b
Nova has enabled the scope checks and new defaults in
antelope release and now devstack is switching the testing
to new defaults by default (depends-on). With that all the
jobs will run the the new defaults.
As old defaults are still supported (as deprecated), we should
test those at least in a single integrated job. Adding
new job tempest-integrated-compute-rbac-old-defaults to test those
old defaults.
Keeping existing job enabling the new defaults because other services
have not switched to new defaults yet to this job enable new defaults
for those service and test Nova against that.
Depends-On: https://review.opendev.org/c/openstack/devstack/+/883601
Change-Id: Ifc3d0abe3e4caab701b695d3781f20ab3dba267d
The recent change(s) to enable a lot more SSHABLE checks puts the
runtime of the ceph job really close to the 2h timeout even when
things are working. Sometimes it times out before it finishes even
though things are progressing. Bump the timeout to avoid that.
Also bump us to 8G swap to match what is set on the parent ceph job
when we upgraded to jammy. We could just unset this, but better to
pin it high in case that job (defined elsewhere) changes. Our job
is the largest ceph job, so it makes sense that it keeps its own
swap level high.
Change-Id: I6cefd87671614d87d92e4675fbc989fc9453c8b9
Neutron also flipped to python>=3.9 on all their repos this morningi[1]
which means we can't install neutron on focal at all. I'm not sure if
that's going to get reverted at this point, but even if it is, it's
going to take a while to undo. As noted in the comments and the
original commit[2] that added this job, it was intended to be removed
when we dropped focal from the test interface, which we have now done.
1: https://review.opendev.org/q/topic:bug%252F2017478
2: https://review.opendev.org/c/openstack/nova/+/861111
Change-Id: I5be638a702629e07ec9c88bd67bb9b7f1212f7fc
This makes us test N-2->N even for non-SLURP releases. Ideally we
would continue to keep this working, even though we don't have to.
But, even if this highlights some breaking change and we have to drop
this job, the sentinel will be useful.
Depends-On: https://review.opendev.org/c/openstack/grenade/+/875990
Change-Id: I2b21e7d5f487f65ce4391f5c934046552d01a1e2
This job is known to fail due to OOM in various places, so this makes
it enable the memory footprint reduction flags for devstack that we
already use in the ceph job.
Change-Id: Ibf1bdb55018a329075e31058f83ab95331c84ebb
This makes the ceph-multistore job use the MYSQL_REDUCE_MEMORY
flag in devstack to try to address the frequent OOMs we see in that
job.
Change-Id: Ibc203bd10dcb530027c2c9f58eb840ccc088280d
Closes-Bug: #1961068
As discussed in PTG, we need to test the new RBAC in the
integrated gate and accordingly enable the new defaults
and scope check by default. A new integrated testing job
has been added and results show that the new defaults and
scope checks are working fine. During testing, we found a
few bugs in neutron policies but all are fixed now.
enforce_scope and enforce_new_defaults are oslo policy config
options but they are per service level and the default value
can be overridden. Oslo policy 3.11.0 version allows to override
the default value for these config options[1] so upgrading the
oslo policy version in requirements.txt
Depends-On: https://review.opendev.org/c/openstack/devstack/+/869781
Depends-On: https://review.opendev.org/c/openstack/placement/+/869525
[1] https://github.com/openstack/oslo.policy/blob/3.11.0/oslo_policy/opts.py#L125
Change-Id: I977b2daedf880229c8d364ca011f2ea965b86e3a
A few tests related to volume detach are timeout in
nova-lvm job (failing 100%[1]). Root cause of timeout is not
known and it may take time to find and fix the issue. To unblock
gate and keep runing rest of the tests in lvm job, let's skip
the failing tests until they are fixed.
Related-Bug: #1998148
[1] https://zuul.opendev.org/t/openstack/builds?job_name=nova-lvm&branch=master&skip=0
Change-Id: Id29ce352df84168d0a45512e2c59820aefc75943
As per 2023.1 testing runtime[1], we need to test on Ubuntu
Jammy (which will be taken care by tempest and devstack patches
to move base jobs to Jammy) and at least single job to run on
Ubutnu Focal (for smooth upgrade). Also, python 3.10 testing is
voting now.
This commit adds a new job to run on focal which can be removed
in future cycle when testing runtime drop the requirement of Focal
testing. Also, make python 3.10 functional and unit test job as voting
(openstack-tox-py310 is running as part of generic template so we do
not need to explicitly add that)
[1] https://governance.openstack.org/tc/reference/runtimes/2023.1.html
Change-Id: Ia43f73dba00b0b5932939bcc7d11b97a83072ee3
This inflates the cirros image to 1G for a more realistic scenario.
Technically we should have been doing something like this all along,
as the deployment guidance for ceph is to use a raw image, not a qcow2
one, so this also increases our accuracy to real-life.
We also need to up the volume size tempest uses for various tests
to make sure we will fit.
Change-Id: I5c447e630aaf1413a5eac89c2e8103506d245221
Centos 9 fips tests are already merged on Nova and Centos 8 jobs were already replaced by Centos 9,
this patch will delete a Centos 8 periodic pipeline that should have been deleted on previous patcc.
Change-Id: Ib735e9b52915639006bb08424d83f8ee39113d4f
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for antelope. Also,
updating the template name to generic one.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: Ieecbed5216c1ed47743bc2b74745c0a91bb105a3
Zuul
yatinkarel
OpenStack Release Bot