* Update oslo.log from branch 'master'
to 3a6bb3ce5c911f13d4bb72b152037a2e9a0e8304
- Merge "Remove fallback for old oslo.context"
- Remove fallback for old oslo.context
The get_logging_values method was added in oslo.context 2.0.0[1].
[1] 22ad2c2c591f16012a75c99bd11b2f30d35bffff
Closes-Bug: #1715148
Change-Id: Idb31334674805e821cf5c34b9553b7002d158b6c
* Update oslo.log from branch 'master'
to 138b0caf84cec2f3dac7d10603dc300556a5d14b
- Merge "Apply eventlet workaround only once"
- Apply eventlet workaround only once
... to avoid issues caused by setup method called multiple times.
Closes-Bug: #1995514
Change-Id: I125f7a8fa12f4d17af70987c20e5dedb14232d7b
* Update oslo.log from branch 'master'
to 1e68ceb2c5b9c576f919f63ab4c83ef68e372d84
- Merge "Validate rate_limit_except_level by choices"
- Validate rate_limit_except_level by choices
... to reject invalid values with explicit errors.
Change-Id: I04d10bb977c4ebdaed7b5a2d159ae9c10897679b
* Update oslo.log from branch 'master'
to b04509248d3fd664329f3f8f73bd62c4f05db50d
- Merge "Imported Translations from Zanata"
- Imported Translations from Zanata
For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html
Change-Id: Ic56a0875702143a71fea68a431cc1eeb80feb7ab
* Update oslo.log from branch 'master'
to 31603ac6dacd0b47ec9f02d99bfdd0a7b683119c
- Deprecate watch_log_file
This feature has been broken for some time without any actual update
to fix it. Also the pyinotify package used hasn't been updated for 9
years and looks badly unmaintained.
Related-Bug: #1740111
Related-Bug: #2059855
Change-Id: If776fee0072d95737e1c19ad673a3c881a89de06
* Update oslo.log from branch 'master'
to a1fe1b9cfb841d632aa582a52c106b4ebab1c159
- Fix eventlet detection
Eventlet may be installed, but not used for example projects
like octavia. Improve autodetection mechanism by trying to import
module and check if it is actually patched.
Closes-Bug: #2039346
Change-Id: I860abe953ce945bb5152c77a7daeb6aa1003512b
* Update oslo.log from branch 'master'
to 3e58709e8035d32bb37415b665b8a49dc89552e2
- Merge "reno: Update master for unmaintained/victoria"
- reno: Update master for unmaintained/victoria
Update the victoria release notes configuration to build from
unmaintained/victoria.
Change-Id: If991ba29c68011a7a1d76b13e7c3abab52d05f9f
* Update oslo.log from branch 'master'
to 66285911c06a78dd3fbdc7e4ce7a0d5875291ed9
- Update master for stable/2024.1
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: I4f35c60e6b4605bc09eadf51c97ca118221afc21
* Update oslo.log from branch 'master'
to a892465f1947b952c7d0db468b09a9dc7e8f40bc
- pre-commit: Integrate bandit
We also remove these unnecessary linter dependencies from
test-requirements.txt.
Co-Authored-By: Stephen Finucane <sfinucan@redhat.com>
Change-Id: Ie797e48fb9d04649fa70e3d5c2f4161d123ed8f5
* Update oslo.log from branch 'master'
to de07539a7b93f307bc6ee2fe54734f852ac746ec
- pre-commit: Bump versions
hacking now has a native hook.
Co-Authored-By: Stephen Finucane <sfinucan@redhat.com>
Change-Id: Ib7af2d4299853e9758cbf148908aa1ef5de1b235
* Update oslo.log from branch 'master'
to 631b2f62dcc3152a7a1bd08e3db1330c13e372f5
- Bump hacking
hacking 2.0.x or 3.0.x is too old.
Change-Id: If6b2d64febbf00814503eccd59dd9dadd330e0ba
* Update oslo.log from branch 'master'
to fddcbf13651a355ed020e2ad7093037312788287
- Update python classifier in setup.cfg
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: Ie93ba0a3b817944b9ca801590c02d3900c23cde6
* Update oslo.log from branch 'master'
to ca1ef3b8c93251f4847ff1f4a3828798a6202c35
- Update master for stable/2023.2
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: I8edfee12910034cbff318131654ffe00de8396c9
* Update oslo.log from branch 'master'
to 0b478677025f713f55b59ded213cc512f0a77b5a
- Merge "Catch RuntimeError when loading log config file"
- Catch RuntimeError when loading log config file
Since python 3.12, logging is raising RuntimeError when content is
invalid [1][2]. Note this is also backported to 3.11 branch.
This is making oslo_log to not raise LogConfigError but throw the
underlying RuntimeError.
[1] 152227b569
[2] 12f1581b0c
Change-Id: I7631394bee7281f6a393ab4ba7604f871626997a
* Update oslo.log from branch 'master'
to eaf6089ab23d347dbe5ca660db74d646064269ae
- Imported Translations from Zanata
For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html
Change-Id: If54645a47ec9bc193215550f4f37e3f8a3ab131a
* Update oslo.log from branch 'master'
to 6abf69e194c9dac13d26bca3e7ac1f710f9e26a0
- Moves supported python runtimes from version 3.8 to 3.10
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: Ibabaaf286ca4ce942908086e490929900ccf7c95
* Update oslo.log from branch 'master'
to ecfe66faa1a475b2cffb8227a2fb1217c9d9530a
- Update master for stable/2023.1
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: I8e979b65ca350f53b6eb795f5d2358c628268425
* Update oslo.log from branch 'master'
to 76f3098ac07a72c514344d124e3cab2e1435cb36
- Merge "Cleanup py27 support"
- Cleanup py27 support
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7 stanza from setup.py
Change-Id: I82753bf268ebcc6fd701a56c64534a9cd3d5b4ae
* Update oslo.log from branch 'master'
to 15c71dd60497cb89c22579aaf1016a909cb21ac4
- Imported Translations from Zanata
For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html
Change-Id: If528578c75c86ab560b19a53e32fca921c827878
* Update oslo.log from branch 'master'
to de615d9370681a2834cebe88acfa81b919da340c
- Make the eventlet logging fix execution conditional
This patch changes the ``log.setup()`` signature to allow a kwarg
that makes the eventlet logging fix conditional.
Some libraries that import oslo.log, replace the logging locking
handling with its own implementation. For example oslo.privsep
replaces the logging handler with its own one [1], that allows the
communication between the privileged daemon process and the service
importing the library. This local handler clashes with the
evenlet logging fix implemented in [2].
[1]1020c6fbf5/oslo_privsep/daemon.py (L579)
[2]https://review.opendev.org/c/openstack/oslo.log/+/852443
Partial-Bug: #1995514
Related-Bug: #1995091
Change-Id: I4bbcfe7db6d75188e61b9084cb02b2dd2aaa0c76
* Update oslo.log from branch 'master'
to 94b9dc32ec1f52a582adbd97fe2847f7c87d6c17
- Fix logging in eventlet native threads
There is a bug in eventlet where logging within a native thread can lead
to a deadlock situation: https://github.com/eventlet/eventlet/issues/432
When encountered with this issue some projects in OpenStack using
oslo.log, eg. Cinder, resolve them by removing any logging withing
native threads.
There is actually a better approach. The Swift team came up with a
solution a long time ago [1], and in this patch that fix is included as
part of the setup method, but will only be run if the eventlet library
has already been loaded.
This patch adds the eventlet library as a testing dependency for the
PipeMutext unit tests.
[1]: 69c715c505
Closes-Bug: #1983863
Change-Id: Iac1b0891ae584ce4b95964e6cdc0ff2483a4e57d
* Update oslo.log from branch 'master'
to 6401da71b3b1b8d0fc213f0a58dbf69031acba87
- Merge "[Fix] init global_request_id if not in context"
- [Fix] init global_request_id if not in context
Initialize by default the `global_request_id` if not passed
in the given context to avoid error with logging.
Change-Id: I6bd63c1d6a1331a4e47b923ccf6df50c930c8162
Closes-Bug: #1972974
* Update oslo.log from branch 'master'
to cdbf6e7a915059df7820b41a989adce09969834c
- Drop python3.6/3.7 support in testing runtime
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)
Change-Id: I46e2456b9931d215c97b15ac97b47a6977282584
* Update oslo.log from branch 'master'
to ebdee7f39920ad5b4268ee296952432b0d41a375
- Merge "Log Global Request IDs by default"
- Log Global Request IDs by default
Global Request IDs were introduced a while ago[1] so that operators can
trace processing of resources across multiple services more easily.
Some services like Nova or Neutron have implemented this feature and
a request made by these services have additional global request id in
its context. However current default format doesn't include that new id
and users need to update the log format parameter in each service to
get this information recorded.
This change updates the default log format so that the Global Request
IDs can be more widely and easily used.
[1] https://specs.openstack.org/openstack/oslo-specs/specs/pike/global-req-id.html
Change-Id: I1adc9b29bb356ce56704c066b375b49374200d3c
* Update oslo.log from branch 'master'
to 7ed065f38df0595881d07eb91cec9e5c07cb38be
- Add system scope information to default user identity string
As part of Secure RBAC work, support for system users(eg. system admin)
is being added. However current default format does not include
the system scope information so we can't determine whether the context
is non-scoped or system-scoped.
This change updates the default logging_user_identity_format so that
system scope is logged by default.
Change-Id: I7982cdb280599fb38362eb837cb527592267b91f
* Update oslo.log from branch 'master'
to f31946fd8925887ae026e99a504866339c1806de
- Merge "Fix formatting of release list"
- Fix formatting of release list
Change-Id: Ibd6deb5339129e8f4099bdb1fef48490a8bac093
* Update oslo.log from branch 'master'
to 264108395acc38c333f1a859736d97a6a294927c
- Merge "Add Zed in versionutils"
- Add Zed in versionutils
with these once could use versionutils.deprecated.ZED
in config annotations and logs.
Change-Id: I8d5ed01a4b4d1a544fe868c571a54dc96e8ae2f2
* Update oslo.log from branch 'master'
to be33d589d026443b61aebef5abd097336c84669d
- Update CI to use unversioned jobs template
As part of the migration of this project to the independent release
model, we failed to notice that the job template was still tied to a
specific release. We've now introduced a new unversioned job template,
'openstack-python3-jobs' [1], which was can and should use. Do this.
[1] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/833286/
Change-Id: Id3cc1d93e18a172960b4c8ca7a7e52ebfd307842
Depends-On: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/833286/
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Update oslo.log from branch 'master'
to 0a4ed949fa11df5887e2aa519e8842dbbed73b1d
- Add Python3 yoga unit tests
This patch updates the project template to use the Yoga project template
to ensure unit testing is in place for all of the tested runtimes
for yoga. For more please refer to [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: Idda4215001b245322983d59507a38d19d1d322bd
* Update oslo.log from branch 'master'
to de03a59ed78e3e5d97d530918a4a1680160660dc
- Add Yoga to versionutils
Change-Id: If1e846c79477cb0fc06d5702240e1dbb9f2c9c40
* Update oslo.log from branch 'master'
to 650ce7d313e00525c4391692fbdc4cba529e11ea
- Use project when logging the user identity
The logging_user_identity_format option's default value is changed
to reference the project instead of the tenant. This is necessary
because I2fded6f3476df1fb8c4e042ef28ed8ccb7ab0737 removed the tenant
argument from request contexts.
Related-Bug: #1505827
Change-Id: Id6d4b6eaa2b96ba5bd53e8b2dae5d9eea13b25d9
* Update oslo.log from branch 'master'
to 96a08b8ff9ac5ad9e4c61a09daa9517d4b734e6b
- Replace deprecated arguments of RequestContext
The following arguments of the RequestContext class are deprecated
since oslo.context 2.18[1].
user : renamed to user_id
tenant : renamed to project_id
domain : renamed to domain_id
user_domain : renamed to user_domain_id
project_domain: renamed to project_domain_id
This change updates arguments used accordingly.
[1] d78cf592e1e3e7aa0fc99bfdd655e82f5c44dfe3
Change-Id: I815790106e42ca3cb5b8b3cf98b065a27b9a520e
* Update oslo.log from branch 'master'
to 41c8807534a85d6c5eee1dd05a24eb5044f696e1
- Merge "Remove references to 'sys.version_info'"
- Remove references to 'sys.version_info'
We support Python 3.6 as a minimum now, making these checks no-ops.
Change-Id: Ifd84fe4d7282e93998dc37cab4adda6d99d4adc1
* Update oslo.log from branch 'master'
to 72f5eb88e4bc6ca9cbf2a05a7328b0a03dab90d5
- Merge "Ussuri+ is python3 only"
- Ussuri+ is python3 only
update python to python3
Change-Id: I08e9b66e03c59af7f6600633aaa87d55fcd46a56
* Update oslo.log from branch 'master'
to dc9fe87b7394cf4588f57e2b8d85b711fab3f00a
- setup.cfg: Replace dashes with underscores
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: I19543673ddf80d93e28f5503b7672f64a6cecf2a
* Update oslo.log from branch 'master'
to 349d9dd9ee7253c48c1924724c55e65591c8dbd0
- Merge "Drop lower-constraints"
- Drop lower-constraints
Lower-constraints is not a requirement of the OpenStack Python PTI
[0] and there currently is a discussion on the mailing list [1]
about dropping the test, with the oslo team already having done
so [2].
The new dependency resolver in pip fails due to incompatible
dependency versions in our lower-constraints file, meaning that
we were never providing any real guarantees with it.
To unblock the CI, I am disabling lower-constraints job for now,
with the option to reenable it in case we fix the constraints,
and based on the outcome of the mailing list discussions and
consensus.
[0]. https://governance.openstack.org/tc/reference/pti/python.html
[1].
http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019672.html
[2].
http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019659.html
Change-Id: I04e49f005841eb341c2d53cbc469252c089d1ab5
* Update oslo.log from branch 'master'
to b8ccdcf9e9f8be4f7c57f43e4245fdc58cdc14ab
- Merge "Fix log_rotate_interval help text formatting"
- Fix log_rotate_interval help text formatting
Add a missing space, this currently generates
"setto" in config files.
Change-Id: I4086fcab1e96e9127d7fe084d887cf57c8f87828
* Update oslo.log from branch 'master'
to 127b3589233e769d3a19d2978a694f4bfcc59f1c
- Merge "Add Xena to versionutils"
- Add Xena to versionutils
Adding warrior princess release to the list of releases. :-)
Change-Id: I6bf6997899f6c95ed1074563164b82fce37f26f3
* Update oslo.log from branch 'master'
to 0d62939520eb919baf19aafcc26e729a7ec9c456
- Merge "Use TOX_CONSTRAINTS_FILE"
- Use TOX_CONSTRAINTS_FILE
UPPER_CONSTRAINTS_FILE is old name and deprecated
This allows to use upper-constraints file as more
readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>.
[1] https://review.opendev.org/#/c/722814/
[2] https://zuul-ci.org/docs/zuul-jobs/python-roles.html#rolevar-tox.tox_constraints_file
Change-Id: Ic4b4627cf0bbd401c870f813f2a5884950c7cb6a
* Update oslo.log from branch 'master'
to bc37c62ce778ada2516b7d842219f0d207be9243
- Dropping lower constraints testing
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: I339b18e533c75283c58409a2cdce001e4b5fbb18
Zuul
OpenStack Release Bot