As per 2025.1 testing runtime[1], we need to test on Ubuntu
Noble (which will be taken care by tempest and devstack
patches to move base jobs to Noble (depends-On)) and at least single
job to run on Ubutnu Jammy (for smooth upgrade from previous
releases).
This commit keep rbac default job continue running on Jammy
which can be moved to noble in next cycle.
Depends-On: https://review.opendev.org/c/openstack/tempest/+/932156
[1] https://governance.openstack.org/tc/reference/runtimes/2025.1.html
Change-Id: Id1d9282ede1c89ce71db18dccf9a37bd3e058edf
This reverts commit 704b24fd67b6d3dee5f1f42f9b793832b4b47bf4.
Reason for revert: We can revert this as the main fix is released now
https://review.opendev.org/c/openstack/releases/+/933578
Change-Id: I013e5a90a4dd5b6ba436b9f57ffe88fdc29eb326
This is a workaround to set the default volumes quota to 50.
The correct way is to release the openstackclient fix[1].
Until the OSC fix is released, this patch will unblock gate.
[1] https://review.opendev.org/c/openstack/releases/+/933578
Change-Id: Iaafcbd4ff858bf905b51d80bfda89e8a59b235e4
RBAC config options enforce_scope and enforce_new_defaults
were disabled by default in oslo.policy and Glance had to override
the default value to enable those by default. Now oslo.policy
(4.4.0 onwards[1]) changed the default values[2] and enabled
by default for all the services. OpenStack service does not need
to override the default anymore.
As every job run with glance new defaults:
- Removing glance-tox-functional-py39-rbac-defaults
- Add new periodic job to test old defaults
- tempest-integrated-storage-rbac-old-defaults
NOTE: There is no change in behaviour here, oslo.policy provides the
same configuration that Glance has overridden till now.
[1] https://review.opendev.org/c/openstack/releases/+/925032
[2] https://review.opendev.org/c/openstack/oslo.policy/+/924283
Depends-On: https://review.opendev.org/c/openstack/requirements/+/925464
Change-Id: Ib9a503783df6fb40058089319c7c8b7e9d89d3b8
This reverts commit 244ccb68dd9c1be8b8c6223c50998464a394b688.
Reason for revert: disk-format list not required to be passed to the import jobs after the tempest change [1].
[1]: https://review.opendev.org/c/openstack/tempest/+/924252
Change-Id: Id2548fad3e90144b47964b82bb4f702ad6407ae2
The openstack-tox-functional-py38-fips job is based on centos-8-stream,
which is no longer working and will soon be dropped completely, so
remove the job.
Change-Id: Ie419f2cf9f685bba770b6b2c88571e41758cb212
This reverts commit b75f3e4a4278f71d5379d40858df49c8920ca53d.
Reason for revert: Since we have landed all important patches on master branch, we can now revert this change and make jobs voting.
Change-Id: I2f5fa707a2cb7f6ffb38a8b919f224897684c795
The tempest-integrated-storage-import has been timing out
frequently around 2 hour 5 minutes mark and similarly one
of the jobs inheriting from it,
tempest-integrated-storage-import-standalone, also times
out around the same time. The timeout issue has increased
recently as can be seen in the job build history[1].
We had a similar issue with the glance-multistore-cinder-import
job for which we increased the timeout to 3 hours[2] but the
job completes successfully on average 2 hour 10 minutes
and has been completing in that time for more than 8 months
since the change to increase timout landed.
The underlying cause could be due to a lot of reasons:
1. Lower concurrency (3) as compared to parent job (6)
2. More number of tests being added to tempest
3. Slow Devstack installation
4. Slow tempest test execution
5. memory consumption of OpenStack services
increased making environment slow
6. no significant improvement in the hardware
specifications on which we run the job
This patch generalizes the timeout to the tempest-integrated-storage-import
job so all of it's child jobs also don't face similar timeouts.
Also we are updating timeout for tempest-integrated-storage-enforce-scope-new-defaults
job as we see similar time out issues in that job.
[1] https://zuul.opendev.org/t/openstack/builds?job_name=tempest-integrated-storage-import&skip=0
[2] 64e6da6fe1
Change-Id: I7165bb8c588659362b7b36394111c41772ac802d
Recent changes does not allow image conversion to convert an image
having AMI disk format for image. Passing list of disk-formats to
each import job which will now use qcow2 as default disk-format to
create the image.
Change-Id: I712b304ebe168705ec2793626f5d64135ad6d458
This job will verify that upgrading cache driver from sqlite to
centralized database will not have any impact.
Related blueprint centralized-cache-db
Change-Id: Iafed7342753da73efee2c50079505d88fe8ac4d5
Temporarily make the openstack-tox-functional-py38-fips
job non-voting till we figure out why its failing.
Change-Id: I8b693a692fc1248c385cfa7d0808ae0283a33781
This reverts commit caa6e5d965c1467d7df51ceaa29660fe5140f1c3.
Reason for revert:
Sqlalchemy issue is fixed and upper-constraint change is also merged after oslo.utils 6.3.0 release.
Change-Id: I21e3911aaea363dfd2d46974431bf34efd72282d
zuul now says:
All regular expressions must conform to RE2 syntax, but an expression
using the deprecated Perl-style syntax has been detected. Adjust the
configuration to conform to RE2 syntax.
Do as we're told.
Change-Id: Iffa8ae6102c547184fab4ed0f6860a5a73da150c
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
Ubuntu focal was in testing runtime as best effort
testing in 2023.1 cycle. In 2023.2, we do not need to
test the focal as such. Removing its testing to more
focus on making Jammy testing more stable.
[0] https://review.opendev.org/c/openstack/tempest/+/884952
Change-Id: I9f621ac4984d78e5e6a5ff0a0abc493cc9f7bf07
glance-multistore-cinder-import-fips which is using centos is
broken recently.
A temporary workaround is to set the GLOBAL_VENV to false
specifically for centos 9 stream distros where the issue
is encountered after changing the default value
of GLOBAL_VENV to True in Devstack:
https://review.opendev.org/c/openstack/devstack/+/558930
Change-Id: I5ea80c2708e5adf65129283bbf7d8826843d5c67
CI jobs tempest-integrated-storage-import-standalone,
tempest-integrated-storage-import and
glance-multistore-cinder-import were failing while converting
image from qcow2 to raw. The failures were caused by changing
default behavior of Devstack and installing everything in global
virtualenv patch [1].
This fixes import conversion in the affected jobs properly by setting
the python interpreter to the one in the venv. When we spawn external
commands they actually spawn a python interpreter to use an oslo
module to do the exec, and we need to do that with our venv's python.
Finally, this bumps the swap size for the storage-import jobs to 8G
to help account for the additional overhead of running another glance
worker, which is required for that configuration. This matches other
jobs with additional overhead (i.e. the ceph ones).
[1] https://review.opendev.org/c/openstack/devstack/+/891248
Co-Authored-By: Dan Smith <dansmith@redhat.com>
Depends-On: https://review.opendev.org/c/openstack/devstack/+/892571
Change-Id: I073216d1bbddbd3bdecd2b135e4c291f7a4d9abe
We add a wholly new job rather than modifying one of the oslo-tips jobs
since these jobs are run periodically rather than in the check queue and
we want to prevent regressions.
Change-Id: I1036b7b0d64c91f0f64b37340490a2e52ee0baea
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
Glance 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. Enable the old
defaults in glance-multistore-cinder-import job.
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 Glance against that.
Depends-On: https://review.opendev.org/c/openstack/devstack/+/883601/
Change-Id: I470e3b8c1106d88e85343508a8e5891c88861c98
zuul.yaml file contain many jobs definition and base class.
Any change in this file can impact other job definition. Also,
many times we want to test the full integrated gate if this
file is changed or if depends-on is changing some global setting,
for example: https://review.opendev.org/c/openstack/glance/+/883602/1
Change-Id: I14abd88944407da17ca81b77c079262565ff71c6
Based on the python runtimes for 2023.2 [0], we should be running
functional jobs on python 3.9 and python 3.10. This patch adds
functional testenvs for python 3.10 and 3.11 (the latter for local
testing) to tox.ini so the appropriate zuul jobs can be defined.
The functional-py38 testenv is not removed from tox.ini, as it may
be useful locally.
Functional py39 and py310 jobs are added to the check and the gate.
The current openstack-functional-py38-fips job is not removed; a
py39 job has not yet been defined to replace it [1].
[0] https://governance.openstack.org/tc/reference/runtimes/2023.2.html
[1] b3cad4f7a3/zuul.d/jobs.yaml
Change-Id: Ibc21b107878f5ba50137da4082a7cbc6342d2aa9
Tempest change [1] has broken glance srbac tempest tests, so
in order to unblock the gate we need to turn the job non-voting and
once we fix those tests we will re-enable the same.
[1] https://review.opendev.org/c/openstack/tempest/+/871018
Change-Id: Ibbfd8904b3a87b870ed8cde26245176c5b8e74aa
Since openstack release naming conventions has changed, current test
which check data migration version will not work as expected and same
is also blocking our gate. Removing this job and test to unblock the
gate.
NOTE: Going forward glance PTL/team needs to change the database
migration version without fail at the start of release cycle.
Change-Id: Idcb12a6c450d4ce4ee859e6e1f02fb71adf8c1d5
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: I9c3e19cf1a2c74381395d49ee3d792bbd92b603a
The ecdsa usage for ssh is supposed to be the default right now.
Also, a new role paramter nslookup_target is required for the fips role
Depends-On: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/847193
Change-Id: I795c751edd1403d23aa1de5cda194aada80d05b2