| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Update IBM copyright strings to one consistant format
Change-Id: I838321f9126d78818bae9ba0c79615b5f2d71226
|
|\ \ \ \ |
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
PathFilter is a type of filter that allows to check
if path arguments of a command resolve to file system
paths within given directories.
Fixes bug 1098568.
Change-Id: Ie2686ad2ff114075c6d8d804031b6e3fa60a43ca
|
|\ \ \ \
| |_|/ /
|/| | | |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes bug #1160475.
Positional arguments were dropped during the deserialization of
valid remote exceptions, while keyword arguments are correctly
supplied.
Change-Id: I7b95fc4ed3fb9e5c75f5711ed6aace7aa5593727
|
|/ /
| |
| |
| |
| |
| |
| | |
One of the problems with fakes is that sometimes you can fake away
a bug and have happily passing tests and broken code.
Change-Id: Ib544739699b63d3f5e80edc16e19377d45782334
|
| |
| |
| |
| |
| |
| | |
Fixes bug 1161679
Change-Id: I4b64fccbb7871dfab4fb74534514aa269c31f03d
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
sql_connection contains the password in some setups and marking as
secret prevents accidental logging
fixes bug 1160680
Change-Id: Ib2d00219ea40a010c62e6a29045309f030e6de28
|
|\ \ |
|
| |/
| |
| |
| | |
Change-Id: I1d0458ecb1314c941d8c72a54c76f9e554ef4348
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes bug #1076285
When oslo-incubator code gets copied into a project, the project's
l10n infrastructure will extract translatable messages from the
oslo code into the project's message catalog. Translations of those
messages will not be found if we use 'openstack.common' as the
translation domain.
Instead, use 'oslo' as the translation domain and update.py will
change this to the project name.
Change-Id: I7ab46c4f860c9c307758ab63002ae410e4f975fe
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Now that Havana has started, remove deprecated Grizzly features
* deprecated alias list_notifier_drivers (for notification_driver)
* openstack/common/notifier/rabbit_notifier.py (use rpc_notifier
instead)
Change-Id: I0dbb997ba774f58766bddf950049ec1e2d5b79de
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The following should use ints not strings.
* matchmaker_heartbeat_freq
* matchmaker_heartbeat_ttl
Fix bug 1159889
Change-Id: If2ce034d2a9876dbe6b232a1f5d73367d29074b0
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
looks like we were setting the wrong param
Fixes LP# 1158807
Change-Id: Id138926f737ce87618d625aa8b289c508a66aaf4
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Co-authored-by lines are the way we've decided to indicated shared
authorship of a patch, so content from them should be included in
the generated AUTHORS file.
Fixes bug 1158319.
Change-Id: I9dacf78c01f3ad74e696f16a7aa39edb98e8d185
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes bug 1158179
In the case that the lock_path does not exist and there is a contested
resource then the process that was waiting on the lock will not
be locking due to the fact that the directory was deleted.
Change-Id: I75d720d4df499e85386d3e2cc86b927b017e12ac
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Because we need compatibility with Grizzly (N-1 support), this should be
reduced to two copies for Havana, before stripping down to a singular
copy for I.
The '-reply' request has its context key removed, with the
msg option maintaining one extra copy of context until I.
A TODO has been entered to clean this up following the Havana release.
This fix eliminates an extra JSON double-deserialization routine.
The double-serialization of context is still performed for Grizzly
compatibility.
fixes bug 1156956
Change-Id: I071e382ec9c7e0df3794fe9ca574a5722f8910a6
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This patch moves the traceback for an rpc timeout from inside an
iterator, which gave a useless traceback, into the main flow of the
program.
It also adds the rpc method being called and the topic used to the
exception's message.
When the caller logs the message higher up the stack, the log
information and traceback will be more useful.
Finally it removes the timeout logging in the amqp.py module, in the
spirit of bug #1137994 and https://review.openstack.org/#/c/23295/
Works towards: bug #1148516
Change-Id: I29a3b1b97c6114c4479e2b71c1257c4d72131535
|
|\ \ \ \ |
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
Grizzly had the ability to receive messages with an envelope, but did
not send them. Now update the code to send them.
Change-Id: I73aad7697cf83ad4aabb3c2058b7cc4f53f783c2
|
|\ \ \ \
| |_|/ /
|/| | | |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes bug #1154245
If the parameter to the --log-config option cannot be loaded by the
logging.config.fileConfig() function, you get an exception like this
raised:
NoSectionError: No section: 'formatters'
which doesn't do much to help users understand the error.
Improve the situation by wrapping the error in a custom exception type
giving this:
LogConfigError: Error loading logging config /etc/logging.conf: No section: 'formatters'
Also add some tests to check we raise this error under the most common
failure conditions.
Change-Id: I6ad2eb4867213b6356ce43d75da50218d1b498f6
|
|\ \ \
| |/ /
|/| | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
This fix allows someone using openstack.common.wsgi to pass
kwargs down to eventlet.wsgi.server when calling wsgi.run_server.
Fixes bug 1156930
Change-Id: Id35232f68ee40c5435e157a834fc94d4bbd04970
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Clarify that --log-dir is only applicable for
relative --log-file paths.
Also change the description of --log-file, to be less specific.
By changing "If not set" to "If no default is set", it
allows for a better description given the cumulative nature of
these config settings. Distributors can use this for example
to set a default in a distribution wide config file that is
then indicated by a commented default in a user editable file.
I.E. the following config file is now more accurate:
# Name of log file to output to.
# If no default is set, logging will go to stdout.
# log_file = /some/dist/default/set/elsewhere.conf
Change-Id: I9a39511b6d6cfff907471ab7a6f31c34592a1015
|
|
|
|
|
|
|
|
|
|
| |
fixes bug 1154745
The previous update (https://review.openstack.org/#/c/24103/) missed
header files that contained "OpenStack, LLC". This change corrects the
missed files to reflect the OpenStack Foundation.
Change-Id: I9c6de265267485ef2c82ea7e6d8643e82134d102
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Sockets are created by the zeromq driver
for the topic specified by each incoming message.
Because the topic is arbitrarily supplied by the sender,
path separators in the topic must be illegal.
Fixes bug 1122763
Change-Id: Iccdb9b69e646bfe7665ee34c367fd4019db25f17
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
log.setup() doesn't really initialize root logger, therefore logging
in 3rd party library such as stevedore doesn't work properly. This
patch enable root logger initialization.
Fix bug: # 1073241
Change-Id: I6fa41b2ba41ff97ad0280f8774a26887d294423e
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
One code change, rest are in headers
Change-Id: I73f59681358629e1ad74e49d3d3ca13fcb5c2eb1
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Allow log_format option to be settable by the operator,
as per configure-logging documentation. Thanks to Marcus Furlong.
Fixes LP: #1124716
Change-Id: I15d39b3162643c22ff6c905ecbb2efa06e2d882f
|
|\ \ \ \
| |_|_|/
|/| | | |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes bug 1135539
When SysLogHandler is configured in UDP socket mode, the user
who doesn't have the admin privilege got the unexpecting internal
server error(HTTP 500) in "nova dns-create-private-domain" command.
This bug occurs as the call graph drew below:
|--ProxyCallback._process_data():amqp.py
|--LOG.exception()
| :
| |--BaseHub.switch():hub.py
| |-- clear_sys_exc_info()
|
|--ctxt.reply(None, sys.exc_info(),..)
|
:
|
|--serialize_remote_exception():common.py
|--failure_info#(None,None,None)
The sys.exc_info() is cleared by the clear_sys_exc_info(), but it is
called again by the ctxt.reply().
This patch prevents the internal error and returns the details of
the forbidden error(HTTP 403) which is expected.
Change-Id: I549b4b2365c53c401edc80bbe30bcde249d27b85
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| | |
The Windows Storage Cinder plugin through
the Windows Locks implementation
of the InterProcessLock fails in
attaching/detaching operations.
Change-Id: I682205592e152b3222e04ca3221d25594d134dd9
Fixes: bug #1153966
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Switch to using auth_token instead of auth_ok
Fixes LP# 1152826
Change-Id: I56569c1fa8f29b0474440c40644729d436d41c7b
|
|/
|
|
|
|
|
|
| |
It takes 15 seconds to generate the ChangeLog for nova. Without --stat,
it takes 0.5 seconds. Removing this makes using tox in nova about the
same speed as using install_venv/with_venv.
Change-Id: I626d5e788bfaf1a80b91d845f21af54680f81c35
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Boolean values for capabilities don't work because extra_specs are
all converted to unicode. The scheduler will then check, for example,
if the boolean 'True' is equal to the unicode string 'True', and will
always return False. This patch allows admins to specify '<is> True'
in extra_specs, which will compare successfully to boolean True.
Fixes bug: 1146306
Change-Id: Id0e6dcfb71eb0943a16bba551ec23c4d57206550
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There is complication with re-raising exceptions and our usage of
eventlet. If the code in the exception handler accesses the db or rpc
in the exception handler, it will no longer be able to re-raise the
exception. Using excutils.save_and_reraise_exception() works aorund
this issue.
The most common error is calling LOG.error() or LOG.exception(), as it
is possible for these to go access rpc. There is an option to turn on
notifications for these errors.
Fix bug 845866.
Change-Id: Ic914bba4703200ed114a42e3a55402883b430407
|