| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use a default value of None for facility in OSJournalHandler
class, as is done in the OSSysLogHandler class.
Neutron started failing with a:
E1120: No value for argument 'facility' in constructor call
With a recent release of oslo.log.
Change-Id: I5269b82d219fd2377535120d9d266238d50431b3
Related-Bug: #1871840
(cherry picked from commit 184235c26517598d6e60f4db72e095ba061a0d6e)
(cherry picked from commit c77f3c9aa82364c482be9b37e6d29634273bb90f)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Without SYSLOG_FACILITY log messages from journald forwards the message
to kern.log. This seems to be default behaviour as it treats the message
as kernel message.
This option provides a proper facility to the log message and kern.log
will not be filled up anymore.
Cherry-picked from commit 5b12e66f6283962d96884e4aa3fa7db7d4e062fa
Cherry-picked from commit 82751ce2a2b913a5d107133a15960c9c6d8fd594
Change-Id: I62a32ed46a400b62ead8c1e6e64acee658e2a769
Closes-Bug: #1871840
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.
Until the requirements repository has as stable/train branch, tests will
continue to use the upper-constraints list on master.
Change-Id: I6ad01ffbb5f1ab49fd9c9cc102e44016cf7c0c8e
|
|
|
|
| |
Change-Id: Id487527974c20e20569b7f084c11ac66fff6d25a
|
|
|
|
|
|
|
| |
See the Train python3-updates goal document for details:
https://governance.openstack.org/tc/goals/train/python3-updates.html
Change-Id: Iae43c960b980ba3c1aa83be8844ae2f873f9c186
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Python 3.7 added caching of the log level for calls to isEnabledFor
on a logger[0]. As a result, modifying the logger level directly
can cause a mismatch in behavior if a log call was made prior to
that modification. In our case, we were calling logger.info before
the info level was enabled, which meant the logger cached the fact
that it was not enabled for info-level logging. Even after setting
the level to NOTSET, it was still remembering that it shouldn't log
info messages and that breaks our unit tests on py37. There is a
related issue open against Python[1], but basically the answer there
was "don't mess with logger internals".
The simple fix is to use logger.setLevel for resetting the log level
instead of modifying the attribute directly.
Change-Id: Ifd1300d8e4280df1913f632e964f9458dbb2db55
0: https://github.com/python/cpython/commit/78c18a9b9a1445f7c755929917a790ba02b4a5e0#diff-5bd69232a06838f179312d3e48ccf506
1: https://bugs.python.org/issue34269
Closes-Bug: 1783630
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some options are now automatically configured by the version 1.20:
- project
- html_last_updated_fmt
- latex_engine
- latex_elements
- version
- release.
Change-Id: I61f26bed7831cdcce1f33f3981c3e97b018c4c42
|
|
|
|
|
|
|
| |
See https://github.com/sphinx-doc/sphinx/issues/6440 for upstream details
Depend-On: https://review.opendev.org/#/c/663060/
Change-Id: Ic5fe18b6c0b0b59310b0adbf05c2d6583ff759f4
|
|
|
|
|
|
|
|
| |
Incubator logging has been gone for years. Nobody still needs these
docs, and on the off chance that I'm wrong they're still available
in git.
Change-Id: I4757f93c4194bd821232a2f6cc9abf3be00f15d0
|
|\
| |
| |
| | |
quickly"
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Prepare a periodic job used to check possible issue on requirements
due to the python 2.7 final countdown and requirements
who remove python 2.7 support. We will check it daily
to see potential errors quickly outside the
standard development lifecycle (feature, fix, etc...)
Change-Id: I7773e41ec48246fb56e7366a359c067788c9f5bb
|
| |
| |
| |
| |
| |
| | |
Use the hotness for constraints.
Change-Id: I73e284393ce26c91ea675d5be213ff5e910b4dfe
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Convert the logging guidelines from the previous cross-project spec:
https://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html
so that they read as documentation rather than a spec, in order to
encourage developers down the right lines.
Also port a section on variable interpolation from oslo.i18n. It was
misplaced there because it wasn't specific to i18n, and anyway logs
are no longer translated so it had to be removed from there by
Ib86013ff5e7b.
Change-Id: I3b8299b7a53e9e22c507930aa7a37c81ebcd580e
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Translation of log messages was ceased starting with Pike, but only
the oslo.i18n documentation was only partially updated (by
Ia34ad79ca9), and not this repository.
So remove misleading examples of log translation from this
documentation.
Change-Id: Ib86013ff5e7bd07ddc696da2e4c56ce9d07f0cb6
|
|/
|
|
|
|
|
|
|
|
|
|
| |
We do not need tox_install.sh, pip can handle constraints itself
and install the project correctly. Thus update tox.ini and remove
the now obsolete tools/tox_install.sh file.
This follows https://review.openstack.org/#/c/508061 to remove
tools/tox_install.sh.
Change-Id: I67c50430ced6efcc2f29ec7d8adc871415922d6f
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bandit 1.6.0 accidentally changed how to exclusion list option is
handled and breaks our use of it. Cap to the previous version until
bandit has has fixed the problem.
Sphinx 2.0 no longer works on python 2.7, so need to start capping it
there as well.
Limit monotonic to python < 3.3 and reflect the changes to
openstack/requirements introduced
in change Ib8c1bf08f5fa7463911602b0df19315907c81e04.
Co-Authored-By: Stephen Finucane <sfinucan@redhat.com>
Co-Authored-By: Hervé Beraud <hberaud@redhat.com>
Change-Id: I4c2a19fae55e8cfea2d5ae9603a1fb086b5db1bf
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I35110a02e8b16f9c1d3b44441409db990eb1a23f
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Special characters in regular strings now cause DeprecationWarnings
starting with Python 3.6. This frequently happens with regex strings.
Oslo.log had one instance of a regex string containing '\' that would
cause deprecation warnings in logs. This switches that instance over to
be a raw string to avoid these warnings.
Change-Id: Ia5637f35315127c5cc46e01f5e38eccb094e772d
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Keystone uses versionutils for marking config settings
as deprecated and currently TRAIN is missing as an option.
This change adds the same.
Change-Id: I0307665d468ac90b5208aadf6f85373bc339b44d
|
|\ \ \
| |_|/
|/| | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
All the integration testing has been moved to
Bionic now[1] and py3.5 is not tested runtime for
Train or stable/stein[2].
As per below ML thread, we are good to drop the py35
testing now:
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005097.html
[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004647.html
[2]
https://governance.openstack.org/tc/reference/runtimes/stein.html
https://governance.openstack.org/tc/reference/runtimes/train.html
Change-Id: Ib110f4a3c9475d2655dbf67d28474f54928b142a
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Since process_name value defaults to "MainProcess" a new field cmdline
has been added in order to get information which process (daemon)
triggers the event.
Change-Id: I1d7713ff7de930e40fc5b8ceb2cf2af54082c9cc
Closes-Bug: 1822101
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html
Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: Iaa71673414ac0de6d2fb0875a8e8913f3bf9341c
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add file to the reno documentation build to show release notes for
stable/stein.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/stein.
Change-Id: Ifa64f45d74c133e0f588e8356130842dd561a480
Sem-Ver: feature
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Currently the level and traceback must be present as keys 'levelname'
and 'traceback'. Parameterising these will make the utility more broadly
applicable.
Change-Id: I80c9370081ef8229e8c37f0f86cb7d779e1526ec
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
current help message to log-config-append is a bit misleading:
if the extra logging config is using oslo_log's ContextFormatter
as formatter for some handler, the logging_context_format_string
option and the like do in fact still apply.
Instead, give the `log-date-format` as example option that does apply
when log-config-append is enabled and clarify that some options
are used with ContextFormatter only.
Change-Id: I917cdf8799ac0fb5b49873d5c7bccd957a42f347
|
|
|
|
|
|
|
|
|
|
|
| |
Small cleanups:
* Use openstack-lower-constraints-jobs template, remove individual
jobs.
* Sort list of templates
Change-Id: I8270e6d25a19320bc3c854dfcf56379c52aeec53
Needed-By: https://review.openstack.org/623229
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
exc_info is exception tuple not intended to be printed. It's using to
generate output by logging.Formatter().formatException() instead.
exc_text used to cache this output. So we use handler formatter to get
string from exc_info and send it as EXCEPTION_INFO. EXCEPTION_TEXT is
kept for backward compatibility.
Also adds type validation for journal.send fields to unit tests. Known
types could be gotten from journal.DEFAULT_CONVERTERS. The rest payload
must be either a string or bytes.
Change-Id: Idc0b9edc61b4ec39dc9df0ea8282cc104e4d83c0
Closes-Bug: 1802142
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As of change https://review.openstack.org/619260/ to oslo.policy
a lot of information is logged at debug for every policy check,
which gets to be a lot of information in something like the
nova-api logs which does a policy check per API request. So this
change makes the default log level INFO for oslo.policy.
Change-Id: Ie4a114219a69390efd148b705fad05fd8b9a42de
Related-Bug: #1807747
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: Ibca48daefc917daed3f3f2a83c6d3c4973087289
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
Just a couple of doc things that became out of date due to some
code changes during the review process.
Change-Id: I5820f7940d8d32546174da132db5be5a209a2200
|
|/ /
| |
| |
| |
| |
| |
| | |
openstack-dev was decomissioned this night in https://review.openstack.org/621258
Update openstack-dev to openstack-discuss
Change-Id: Ia42def2fb8ccb5dc91ca0403511e2e30fc9081ab
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On Windows, in-use files cannot be moved or deleted. For this reason,
we need the service itself to take care of rotating logs.
For convenience reasons, we're exposing the built-in rotating log
handlers through a set of config options.
More specifically, we're adding the following new config options:
- log_rotate_interval
- log_rotate_interval_type
- max_logfile_count
- max_logfile_size_mb
Change-Id: I01db4efc08e2cb64db9cbf793f3a159f54859fe7
Closes-Bug: #1802262
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The Python built-in logging module already provides a Windows Event
Log handler. This change ensures that oslo.log exposes it.
Change-Id: I287260b5046c88c433dfa66064da14faf15610e0
Implements: blueprint windows-event-log
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Developers run all sorts of different tools within Git repositories,
any of which can leave their own special trashfiles all over the
place. We can't every hope to catalog them all, so better to
recommend developers simply configure a global core.excludesfile to
filter the irrelevant files which tend to get created by their
personal choice of tools.
To this end, remove the long-standing sections for "Mr Developer"
and "Editors" since their mere existence here sends the signal that
we welcome (and have time to review) additions for any old tool
someone ever might happen to try. Also add a comment block
explaining this, for clarity.
We can, and should of course, continue to list files created by the
tools recommended by our workflow (test frameworks called from tox,
documentation and packaging builds, et cetera).
This change is a port of I1b41efac219fca44e2548fc36633724d0ecfc0cb
from the openstack-dev/oslo-cookiecutter repository.
Change-Id: Ib2c9185265cfe7d2af5afc939f770cf5d5efb6ea
|
|
|
|
|
|
|
| |
All of our projects are pure python, so we can build
universal wheels by default.
Change-Id: I173a1d5b4f204fcda2e92fd751228dbc79009b8c
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We've run into issues in the past where a service passed something
to the logger that broke JSONFormatter. To try to catch those sooner,
add a job that configures the services to use JSONFormatter. This
should provide a more realistic test of the formatter than we can
hope to accomplish in unit tests.
Change-Id: Icfb399cfe3dce89dfd5fb5079295a4947828417a
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In most formatters, any unused keys in the args dict will just be
discarded. Because JSONFormatter logged the entire dict in addition
to the message, some values were included in the output that may
not have been intended. This could include sensitive data, so we
should stop that.
In the interest of maintaining compatibility with any tools that are
reading the args dict, we leave the dict but filter out any unused
keys.
Change-Id: Ib64837c1ae93a27bef3d30a776320a373f18dd1c
Closes-Bug: 1571714
Closes-Bug: 1787214
|
|\ \ |
|