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 caa6e5d965.
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>
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
In Zed cycle, we have dropped the python 3.6/3.7[1] testing
and its support. Moving the py36 job to py38 based as well as
updating the python classifier also to reflect the same.
openstack-tox-functional-py36-fips job is left which can be moved
to py38|py39 based once that job is defined in openatck-zuul-jobs
repo.
openstack-tox-functional-py36-fips job will be migrated to py38 or py39
in followup patch as that need openstack-zuul-config changes too.
[1] https://governance.openstack.org/tc/reference/runtimes/zed.html
Change-Id: Id0813d9dc553dd424732079039349b42f6f3201b
Some projects like cinder have dropped support for Python 3.6 and are
no longer compatible with CentOS Stream 8 which uses Python 3.6 as
the default runtime.
Change-Id: I48f88c188f830f61c03ec5570cd95731636a0396
With change[1], we moved glance cinder jobs parent from
tempest-integrated-storage-import to regular
tempest-integrated-storage job but this job also has
import workflow enabled[2].
In this patch we are overriding GLANCE_USE_IMPORT_WORKFLOW
to False in cinder jobs to ensure that import workflow
is disabled in those jobs.
Also removing -import from job names since it's not using
import plugin anymore.
[1] https://review.opendev.org/c/openstack/glance/+/841548
[2] https://opendev.org/openstack/tempest/src/branch/master/zuul.d/integrated-gate.yaml#L195
Related-Bug: #1973136
Change-Id: I2775e007f942feed8fa6ae5e385c03992859edc1
Recently, glance-multistore-cinder-import job started failing.
As per the RCA done here[1], the reason is glance is using
import workflow to create images which is an async operation.
As in case of glance cinder configuration, there are a lot of
external APIs (cinder) called like volume create, attachment
create, attachment update, attachment delete etc which takes
time to process hence the image doesn't get available in the
expected time (as per devstack) hence the failure.
Disabling import workflow will cause the images to be created
synchronously which should pass the glance cinder jobs.
To disable import workflow, we are inheriting from
tempest-integrated-storage and not
tempest-integrated-storage-import (which has import plugin enabled).
[1] https://review.opendev.org/c/openstack/glance/+/841278/1#message-456096e48b28e5b866deb8bf53e9258ee08219a0
Closes-Bug: 1973136
Change-Id: I524dfeb05c078773aa77020d4a6a9991a7eb75c2
Temporarily make the FIPS job non-voting till we figure out why
its failing. Restore the non-fips version of the cinder job so
we keep the coverage.
Change-Id: I1a9dbd087cca52798f0d01c62ebb47e37f52d87a
Some jobs have been modified to run to confirm that functionality is
still working when FIPS is enabled on the nodes.
As the FIPS tests currently run on centos nodes, code is added
to the test-setup script to set up the databases correctly. Also had
to increase the swap space on the nodes; see [0] for an explanation.
The current FIPS jobs run using python 3.6 on centos-8-stream. We will
modify these to run on centos-9-stream and python 3.9 in a
subsequent patch.
[0] https://review.opendev.org/c/openstack/devstack/+/803706
Change-Id: I060d8247c7b09f63990ea411e6c6a056bb50410d
This adds a new tox target called functional-py38-rbac which enables
the new secure RBAC policy defaults for all functional tests. To do
this, the functional tests needed a little bit of extra work to
actually set those, and a new non-voting job is added to run these
in CI.
Related to blueprint policy-refactor
Change-Id: Id376193521671bdb0ebc08ea8e563578bbaa541f