These are detected as errors since the clean up was done[1] in
the requirements repository.
[1] 314734e938f107cbd5ebcc7af4d9167c11347406
Change-Id: I64bc62373f266ec5f8f853a0d449dd589d1b8183
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: I697bb749ec2008df8c5462e6bdcbdcddb3ed0c97
We also remove these unnecessary linter dependencies from
test-requirements.txt.
Co-Authored-By: Stephen Finucane <sfinucan@redhat.com>
Change-Id: I36a6469231a8ce78f06c9b858d35c161f4d22799
The greenlet library is not always used. It is used to capture detail
of green threads but this part can be skipped in case greenlet is not
present.
Also eventlet in test requirements is not used and can be removed.
Change-Id: I57edfe4d975ce42ca92a9242d4b32e69d1cec268
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: I658cc4e81d57ec16e34d20b3ff26dbb6c92cd04c
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: I1fc7c631f42a9e0cc664eae7684259049686b53b
Some services such as nova introduced GMR for API wsgi application
so that GMR can be generated via a file handler. However the current
setup method tries to register signal handler and causes warnings.
For example we are seeing the following error when starting nova-api
by apache + mod_wsgi.
mod_wsgi (pid=80323): Callback registration for signal 12 ignored.
File "/var/www/cgi-bin/nova/nova-api", line 52, in <module>
application = init_application()
File "/usr/lib/python3.9/site-packages/nova/api/openstack/compute/wsgi.py", line 20, in init_application
return wsgi_app.init_application(NAME)
File "/usr/lib/python3.9/site-packages/nova/api/openstack/wsgi_app.py", line 128, in init_application
init_global_data(conf_files, name)
File "/usr/lib/python3.9/site-packages/nova/utils.py", line 1122, in wrapper
return func(*args, **kwargs)
File "/usr/lib/python3.9/site-packages/nova/api/openstack/wsgi_app.py", line 105, in init_global_data
gmr.TextGuruMeditation.setup_autorun(
File "/usr/lib/python3.9/site-packages/oslo_reports/guru_meditation_report.py", line 152, in setup_autorun
cls._setup_signal(signal.SIGUSR2,
File "/usr/lib/python3.9/site-packages/oslo_reports/guru_meditation_report.py", line 185, in _setup_signal
signal.signal(signum,
This introduces the new argument so that we can disable signal handler
completely to avoid such warnings.
Change-Id: I95170542fecb493260a22d9148f3a2777207cb0e
Within 2023.2 python version 3.9 and 3.10 are the
supported python runtimes [1].
[1] https: //review.opendev.org/c/openstack/governance/+/872232
Change-Id: I6f96568c6dde7347ffd2ca4271414bdfd8b99923
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: Ifa61391b97883ae3d58535e7d6ac91b5334bb3eb
In Zed cycle testing runtime, we are targetting to drop the
python 3.6/3.7 support, project started adding python 3.8 as minimum,
example nova:
- 56b5aed08c/setup.cfg (L13)
Also indicates that we support python 3.9.
Change-Id: I8f917937ea698728ae17fb29f48aa1553caa5eb0
When the config contains a DictOpt that accepts integer keys, the Guru
Meditation Report fails to serialize. Even if current OpenStack code
might not contain such dicts, it's possible that downstream add such
options. Therefore, we change the code to support both dicts with only
integer keys and - just in case - mixed-key dicts.
Change-Id: I44343a8c306c96fc8dc078a76e744cf8b897d8d8
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I8b9c4e1e6fec21134aca37ece8f3881b151d6118
We facing errors related to the new pip resolver, this
topic was discussed on the ML and QA team proposed to
to test lower-constraints [1].
I propose to drop this test because the complexity and recurring pain needed
to maintain that now exceeds the benefits provided by this mechanismes.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019390.html
Change-Id: Ice8c48ed23626538c9a9311a4392d18a3a795b07
flake8 new release 3.8.0 added new checks and gate pep8
job start failing. hacking 3.0.1 fix the pinning of flake8 to
avoid bringing in a new version with new checks.
Though it is fixed in latest hacking but 2.0 and 3.0 has cap for
flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also
break the pep8 job if new check are added.
To avoid similar gate break in future, we need to bump the hacking min
version.
- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html
Change-Id: Ia71dc29dedb6786c4df4546bb4e7df6956966ec0