DB schema upgrade is stuck when SQLAlchemy 2.0 is used because all
operations are not executed within a transaction.
Change-Id: Ief7ea81e78344ea32fb2a295f11a5d5a873251a8
These are detected as errors since the clean up was done[1] in
the requirements repository. Minimum versions are bumped to avoid
installing these known bad versions.
[1] 314734e938f107cbd5ebcc7af4d9167c11347406
Change-Id: I1c2cfb6b8a5fd1521e9d67a28902c657811ff7a7
Add file to the reno documentation build to show release notes for
stable/2024.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.1.
Sem-Ver: feature
Change-Id: Ided9cebfba06011bf76794183335fdb7c3f5bb8e
Resolve the following RemovedIn20Warning warning:
The Engine.execute() method is considered legacy as of the 1.x
series of SQLAlchemy and will be removed in 2.0.
This also allows us to resolve the following RemovedIn20Warning warning:
The current statement is being autocommitted using implicit
autocommit, which will be removed in SQLAlchemy 2.0. Use the .begin()
method of Engine or Connection in order to use an explicit transaction
for DML and DDL statements.
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Change-Id: I46f3277ea17e814e7b631750b2739f25e4395e22
Both the JSONEncodedDict and TimestampUTC can be safely used in a cache
key. Set 'cache_ok' to indicate this. This resolves the following
warnings:
SAWarning: TypeDecorator TimestampUTC() will not produce a cache key
because the ``cache_ok`` attribute is not set to True. This can have
significant performance implications including some performance
degradations in comparison to prior SQLAlchemy versions. Set this
attribute to True if this type object's state is safe to use in a
cache key, or False to disable this warning. (Background on this error
at: https://sqlalche.me/e/14/cprf)
SAWarning: TypeDecorator JSONEncodedDict() will not produce a cache
key because the ``cache_ok`` attribute is not set to True. This can
have significant performance implications including some performance
degradations in comparison to prior SQLAlchemy versions. Set this
attribute to True if this type object's state is safe to use in a
cache ke y, or False to disable this warning. (Background on this
error at: https://sqlalche.me/e/14/cprf)
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Change-Id: I589a0e378e155dcb181e6b1a9cca7aae4cad5349
Resolve the following RemovedIn20Warning warning:
Passing a string to Connection.execute() is deprecated and will be
removed in version 2.0. Use the text() construct, or the
Connection.exec_driver_sql() method to invoke a driver-level SQL
string.
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Change-Id: Ic4518ca1a5aea94a72c9dc3e4393eb970b55c3dd
We aren't passing context objects around, hence this looks more like
ironic's use of oslo.db than e.g. nova or cinder. Nothing complicated
though.
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Change-Id: Ia0368cc128d495011776e80a27af04776e876fa9
The stable/yoga branch has been deleted and replaced with the
unmaintained/yoga branch, update the reno config accordingly.
Change-Id: I2c76cc06f371a284eb3f5d30523add0b7f77b157
tox now always recreates an env although the env is shared using envdir
options.
~~~
$ tox -e genpolicy
genpolicy: recreate env because env type changed from
{'name': 'genconfig', 'type': 'VirtualEnvRunner'} to
{'name': 'genpolicy', 'type': 'VirtualEnvRunner'}
~~~
According to the maintainer of tox, this functionality is not intended
to be supported.
https://github.com/tox-dev/tox/issues/425#issuecomment-1011944293
Change-Id: I8b4f588bfc38aa078bca243ee2ef38f84a92f62d
This follows what was already done in the other projects like [1].
In FIPS mode, md5 is allowed only in non-security contexts. This
change disables the security context in the md5 call to determine
the hash for workload partitioning, because this usage does not
involve any security risks.
[1] 8027d907109b6b3c96623f9793aff752cec8ed12
Change-Id: I7d622a6e7d324a765760819c024295b57990f95c
The zoneinfo module was introduced in Python 3.9. We can use that
built-in module instead of the 3rd party library (pytz).
This is based on change I1f88bdadc68bfa726eac1da1c5824c1ed352ad98 in
oslo.utils.
Change-Id: If6aeb6c837d413c9d9a544a80c4c736efc8455fc
As per the current release tested runtime, we test
python version from 3.8 to 3.11 so updating the
same in python classifier in setup.cfg
Change-Id: I3cd0d2e4ce5bffd6af3cce480a5de09860f5d3f7
... so that operators can review effective values (except for secret
information such as password) from the log.
Change-Id: Ic094df537b5f7333be38c249cdec59a10d2e2660
Remove pifpaf and dependencies to gnocchi for tox test runs.
Remove redundant gabbi tests.
Move wsme & query unit tests from fuctional to unit test folder where
they belong.
Remove integration tests which has been covered in the new tempest
cases in the depends on patch.
Remove run-tests.sh in favour of just calling stestr.
Depends-On: https://review.opendev.org/c/openstack/telemetry-tempest-plugin/+/901838
Change-Id: I5b33cba27dfcb2bbdf12c9bc6b28ecff9aa18d93
This is already done in the 'aodh.tests.functional.db.TestBase' base
class.
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Change-Id: I33e40cdb00620dc67e214f181068d4a024aa1447
None of oslo.context, debtcollector or testresources are used by aodh.
Remove them, along with the warnings about requirements order that no
longer applies with the "new" dependency resolver introduced in pip
20.3.
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Change-Id: I37a1ffe9c9617262eb5e40fc3ad1b02277a11513
This is already listed in requirements.txt so it's not necessary to
repeat it here.
We also remove the Python version classifiers since they're noise:
'python_requires' does this for us in a machine-readable manner
nowadays.
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Change-Id: Ia2c8a5792c175fb0a8762e61ff76383119251cdd
This patch adds threshold evaluator for Prometheus metrics.
Alarms are based on Prometheus query only. The library
python-observabilityclient is used for querying Prometheus.
Co-authored-by: Jaromír Wysoglad <jwysogla@redhat.com>
Depends-On: Ie7477e0b11479449f7f13c7a784737ac70059964
Change-Id: I72e124cca4398b78f7ed12e1db3f66bdbfcb196e
The py311 job has currently trouble locating mysqld.
On debian the mysqld binary is installed to /usr/sbin,
but on debian /usr/sbin isn't in PATH by default.
This patch appends /usr/sbin to PATH.
Change-Id: I89b2631f38e6a7292d6e58b4ddee6f7fdfc6fa9f