Change-Id: I422125b137a3beadb0a79f5944a19fce62f093d6
Closes-Bug: #1887506
(cherry picked from commit 1dc378c7)

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/ussuri branch, tests will
continue to use the upper-constraints list on master.

Change-Id: I98e5447e8a8c9850af5b66d53615926112e64982

Change-Id: I2d33f182f54d7c4b16bdf00a35caee5a2ab93f0f

The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.

Fix problems found.

Remove hacking and friends from lower-constraints, they are not needed
for installation.

Change-Id: I9a2a7c6cd9a0dfd02c6193ceca5653431eed3753

Now that we no longer support py27, we can use the standard library
unittest.mock module instead of the third party mock lib.

Change-Id: Icac647c8e89cd94cae69e357b009d676b1c744f7
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>

There are a couple of things that changed in msgpack 1.0.0 that were
breaking oslo.privsep:

1) The encoding parameter to Unpacker was removed. This has been
   deprecated for a while in favor of the `raw` parameter[0], so this
   change switches to using raw.

2) The strict_map_key parameter default was changed from False to
   True.[1] I haven't found an explanation of why this was done, but
   we can explicitly set it False to maintain the previous behavior.

Change-Id: Ia97ecf965d807f12524d5b6602446934b5813ce6
Closes-Bug: 1855914
Closes-Bug: 1864811
0: https://msgpack-python.readthedocs.io/en/latest/api.html#msgpack.Unpacker
1: https://github.com/msgpack/msgpack-python/pull/392/commits/6e1d12c0a2072572890cbb124b94cb08b582dd2d

This is all necessary to bump the lower-constraint on msgpack so we
can support msgpack 1.0 without version-specific logic in our code.

The reasons for the changes are as follows:

* greenlet and PyYAML bumped because the previous lower-constraints
  for those didn't install on python 3.7, which is a supported Python
  version.
* msgpack-python is removed. It was replaced by msgpack and there is
  no new enough release of it to satisfy the needed minimum version bump.
* oslo.serialization is bumped because the old version was pulling in
  msgpack-python, which overwrote our new needed version of msgpack.
* I went ahead and included the msgpack bump to 0.6.0 so we can move
  forward in the subsequent patch with supporting msgpack 1.0.0.

It could be argued that this should be included in the msgpack 1.0.0
change, but it ended up being complex enough that I thought it was
worth it to split it out.

Change-Id: I69dae65d3e0a40bb2304d74de078ab84fc778d58

The unit tests set format to "dummy", which gets rejected by Python 3.8
by default due to newly added validation here:

  https://github.com/python/cpython/commit/18fb1fb943b7dbd7f8a76017ee2a67ef13effb85

We can skip this and restore old behavior by disabling validation.

Change-Id: I22ba9c4437787c3f338f17a0b006132b0dd09df5

When a neutron agent starts up, it processes different resources
in separate eventlet threads. These can race creating the channel
which results in redundant privsep-helper processes. This patch
fixes that by adding a lock around channel creation.

Change-Id: I5de22b72059133b05d64be47f4c1d3f566b46a6e
Closes-Bug: #1864664

Remove unused noise from the former and unused Sphinx configuration from
the latter.

Change-Id: I754f02fd6eb3c1d77ff2580d53685f4a70da8cc6
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>

Change-Id: Ief0a06e95197b37b47c4ae8cbdff10b4a9fad37c
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>

Change-Id: Ice4e7ef5b05c750e24a10ee1a133d45385341c54

OpenStack is dropping the py2.7 support in Ussuri cycle.

Complete discussion & schedule can be found in
-
http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html
- https://etherpad.openstack.org/p/drop-python2-support

Ussuri Communtiy-wide goal:
https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html

Change-Id: Ia01dfa4bc5d7224bb0f753116cd23bdcc22df146
Sem-Ver: api-break

Move 'basepython' to the top-level 'testenv'.
Use the default 'install_command'

https://tox.readthedocs.io/en/latest/config.html#conf-install_command

Change-Id: Ic951cc21208e54105cfd42fbd28ce1f2f738cced

These add some coverage to functionality not covered by the regular
unit tests, but I think they can't be run in the gate because they
use sudo.

Change-Id: Ic62c95b83f68f94328deb00227b7eabf249ce898

Some options are now automatically configured by the version 1.20:
- project
- html_last_updated_fmt
- latex_engine
- latex_elements
- version
- release.

Change-Id: Ib800f8d30c59adc6f46960c5810cba782839a902

Sphinx 1.8 introduced [1] the '--keep-going' argument which, as its name
suggests, keeps the build running when it encounters non-fatal errors.
This is exceptionally useful in avoiding a continuous edit-build loop
when undertaking large doc reworks where multiple errors may be
introduced.

[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045

Change-Id: I07c753f5070fe887faf4f103b3f46bff59e3d1be

Change-Id: Ib6940a5a72d445be50dfb92d6ae866ddaf4e5d2c

For more detail, see http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006478.html

Change-Id: Ib489b7c28a70463d1ab765da267f6d8fdadb5577

Add file to the reno documentation build to show release notes for
stable/train.

Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/train.

Change-Id: Ie71b1433596dd50876eddd110b427eb4ae08f077
Sem-Ver: feature

Adds a release note for the fix at
I8096fc7fd014e6dd299fae8ab073336c7cae362a

Change-Id: I4682950ac12f763737489c510246d54aed80b80f
Related-Bug: #1715374

When nova-compute, an oslo.service, receives SIGHUP, running PrivContext
clients terminate, resulting in the shutdown of their corresponding
ClientChannel threads. Subsequent attempts to execute privileged methods
fail with EPIPE as a result.

The PrivContext._wrap'per (the meat of the entrypoint decorator) already
had a check to lazily start() the ClientChannel if that hasn't already
happened.

This commit makes ClientChannel store state indicating whether it's
still running; and adds logic to PrivContext._wrap to check that state
and reset (stop() and re-start()) the ClientChannel if it was previously
created but terminated.

Change-Id: I8096fc7fd014e6dd299fae8ab073336c7cae362a
Closes-Bug: #1715374

This is a mechanically generated patch to ensure unit testing is in place
for all of the Tested Runtimes for Train.

See the Train python3-updates goal document for details:
https://governance.openstack.org/tc/goals/train/python3-updates.html

Change-Id: I425e381b3d830ff9d15f8c92bade6cb2a4ee0108
Story: #2005924
Task: #34234

Change-Id: Iedf201e211648452df29fa518c069ecf41a0acf3

six.reraise input arguments are:
  six.reraise(exc_type, exc_value, exc_traceback=None)

This information is provided by sys.exc_info() and stored
in self.communication_error.

Trivial-Fix

Change-Id: Ibe68d8e36ca424da61a0a9eea20e622440c79464

Bandit 1.6.0 accidentally changed how the exclusion list option is
handled and breaks our use of it. Cap to the previous version until
Bandit has fixed the problem.

Sphinx 2.0 no longer works on python 2.7, so we need to start capping
it there as well.

Change-Id: I24a66b454a28d00f96867fa1b24dd408591b41be
Reference: https://github.com/PyCQA/bandit/pull/489

Change-Id: Idd169dc8dbe07a17cbdf3e0834ccf3998badcfb2
Closes-Bug: #1826999

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.