Python 3.11 job run on Debian Bookworm which does
not the mysql pkg for example, mariadb-server, libmysqlclient-dev
instead they have mariadb. Updating bindep.txt file
to adjust the pkgs as per Debian bookworm.
Change-Id: Iddd0dc75f335e3422b1cb2b08897911bb2900662
Add file to the reno documentation build to show release notes for
stable/2023.2.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.2.
Sem-Ver: feature
Change-Id: I5098c5213cc694ef4b3e2d9dbfe76d9e0e156fd5
This option can sometimes contain secrets.
For example when redis coordination backend is used and authentication
is enabled in redis, the plain redis password is put as an URL element.
[DEFAULT]
periodic_coordinator_backend_url=redis://:password@127.0.0.1:6379
Change-Id: I09040b54f6e2ee4f0e71c601400b601b5de19780
Add file to the reno documentation build to show release notes for
stable/2023.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.1.
Sem-Ver: feature
Change-Id: I97460f7d2bb300d0375a3b8d6c99ea8b1af1ab7f
oslo.db 12.1.0 has changed the default value for the 'autocommit'
parameter of 'LegacyEngineFacade' from 'True' to 'False'. This is a
necessary step to ensure compatibility with SQLAlchemy 2.0. However, we
are currently relying on the autocommit behavior and need changes to
explicitly manage sessions. Until that happens, we need to override the
default.
Co-Authored-By: Stephen Finucane <stephenfin@redhat.com>
Change-Id: I5dda36e43caeeb2983cb6a9e0743591fc246d323
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: I0d94b9941a9ab5ee1b03f6ddce84b9c584421d03
As of Zed jsonschema version has been bumped to 4.14.0 in
upper-constraints, which means project should support running with
this version. This patch aims to fix ApiValidator that is not compatible
with new jsonschema.
Other deprecations, like FormatChecker.cls_checks decorator are left
intact and must be covered with follow-up patches.
We also move zuul queues to project scope as otherwise jobs do not
run due to config error.
We also replace iteritems with six method as iteritems have been dropped
from Python 3.
Change-Id: Ia8b69587aa9b3d04ffcdea7c6b97a8ae65f67534
Add file to the reno documentation build to show release notes for
stable/zed.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/zed.
Sem-Ver: feature
Change-Id: I3d3c21992e12045dc0df03459d719f2ac0714669
In Zed cycle, we have dropped the python 3.6/3.7[1] testing
and its support. Removing the py36 centos8 job as well as
updating the python classifier also to reflect the same.
[1] https://governance.openstack.org/tc/reference/runtimes/zed.html
Change-Id: I9b5f826863fd913241cb803ef479b890f74fbb6c
In zed cycle, OpenStack projects and oslo lib
has dropped the py3.6 and py3.7 support
- https://governance.openstack.org/tc/reference/runtimes/zed.html
I also decrepated oslo-log < 5.0.0, so we should bump oslo.log>=5.0.0.
Because of oslo.log>=5.0.0 depends on oslo.i18n>=3.20.0 as below, so we
also need to upgrade oslo.i18n.
The conflict is caused by:
The user requested oslo.i18n>=3.15.3
python-saharaclient 1.4.0 depends on oslo.i18n>=3.15.3
castellan 0.16.0 depends on oslo.i18n>=3.15.3
keystonemiddleware 4.17.0 depends on oslo.i18n!=3.15.2 and >=2.1.0
oslo-config 6.8.0 depends on oslo.i18n>=3.15.3
oslo-concurrency 3.26.0 depends on oslo.i18n>=3.15.3
oslo-db 6.0.0 depends on oslo.i18n>=3.15.3
oslo-log 5.0.0 depends on oslo.i18n>=3.20.0
The user requested (constraint) oslo-i18n==3.15.3
The conflict is caused by:
The user requested pbr!=2.1.0 and >=2.0.0
bashate 0.5.1 depends on pbr>=1.6
fixtures 3.0.0 depends on pbr>=0.11
stestr 1.0.0 depends on pbr!=2.1.0 and >=2.0.0
testresources 2.0.0 depends on pbr>=1.8
testtools 2.4.0 depends on pbr>=0.11
python-saharaclient 1.4.0 depends on pbr!=2.1.0 and >=2.0.0
castellan 0.16.0 depends on pbr!=2.1.0 and >=2.0.0
keystoneauth1 3.4.0 depends on pbr!=2.1.0 and >=2.0.0
keystonemiddleware 4.17.0 depends on pbr!=2.1.0 and >=2.0.0
oslo-concurrency 3.26.0 depends on pbr!=2.1.0 and >=2.0.0
oslo-context 2.22.0 depends on pbr!=2.1.0 and >=2.0.0
oslo-db 6.0.0 depends on pbr!=2.1.0 and >=2.0.0
oslo-i18n 3.20.0 depends on pbr!=2.1.0 and >=2.0.0
oslo-log 5.0.0 depends on pbr>=3.1.1
The user requested (constraint) pbr==2.0.0
The conflict is caused by:
The user requested oslo.serialization!=2.19.1 and >=2.18.0
python-saharaclient 1.4.0 depends on oslo.serialization!=2.19.1 and >=2.18.0
keystonemiddleware 4.17.0 depends on oslo.serialization!=2.19.1 and >=1.10.0
oslo-log 5.0.0 depends on oslo.serialization>=2.25.0
The user requested (constraint) oslo-serialization==2.18.0
Change-Id: I117657e9861a55a751522dba3e3b1e75a22f9711
In Zed, we have dropped the python 3.6/3.7[1] testing
and its support. Removing the py36 centos8 job as well as
updating the python classifier also to reflect the same.
[1] https://governance.openstack.org/tc/reference/runtimes/zed.html
Change-Id: I96076a685482d01ed095803ff716de06afd01816
Python3.6 and Python3.7 are no longer supported by zed cycle tests, and Python3.9 was added when Python3.6 and Python3.7 were removed.
Change-Id: Ie3f0da2775b59df8d01e560b4e507cd331948ae7
It has been reported that "the various test cases and mixins
in 'oslo_db.sqlalchemy.test_base' have been deprecated since
oslo.db 4.34.0 (March 2018)." so migrate to a more stable
and supported solution.
Change-Id: I89aff35352406c0895d379ef6548b406572d076d
Since Flask 2.1, the same blueprint cannot be registered multiple
times with different url_prefix values, unless the 'name' parameter
is set. Otherwise the following error is reported: "The same blueprint
cannot be registered with the same name. Use name= when registering
to specify a unique name."
At the same time, disable the openstack-ansible job,
which started to fail again, but at this point the priority
is to unblock the gates.
Change-Id: I50df2fec3fd312082a14ef2a5b6774a2515afb44
This should allow testing of un-merged changes to sahara in the
context of an openstack-ansible deployment
Story: 2009081
Task: 42894
Depends-On: I1bde4186335cb6638d2c90f5eeee1cf7944e1415
Depends-On: I123d32a0967d5196723f57a40ab5acfa7a53a440
Change-Id: Ib6e09ab83b277704a603c02f0927054478cef8a7
The user property of oslo_context.context.RequestContext has been
deprecated in favor of the new user_id property. This change replaces
reference to the deprecated user property.
Change-Id: Ib5ca9b82970d217df5133b2498c3577af0e60dd9
The tenant argument of RequestContext is no longer available since
oslo.context >= 4.0.0 . This change fixes the compatibility issue
caused by that removal.
NOTE:
Because scenario jobs are still broken with this change, these jobs
are made non-voting temporally to unblock the other jobs. Currently
this issue is blocking package build in RDO.
Story: 2009921
Task: 44779
Change-Id: I1bc81b3c13d2c08bc175d0d4f4365de7b4f71cf9
Add file to the reno documentation build to show release notes for
stable/yoga.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/yoga.
Sem-Ver: feature
Change-Id: I19ad0bec22f1715f384a9737bb5d7c5eab14f8a7