These were missed in change : Icd090cf8a36fa560bf7b0c67d0e1c4923c221c65

Conflicts:
  lower-constraints.txt

NOTE(stephenfin): Conflicts are because the constraints are different.

(cherry picked from commit ad720c33)
(cherry picked from commit 0646eb65)
(cherry picked from commit 1e40b7c4)

NOTE(ajya): Added to fix mysql8 support for requirements-check job
(cherry picked from commit 7af699e7)

Change-Id: I07b577f4e948c03d1751145e5f898b90ac1c197a

Followup of change: Ic78059b625e73cece355541cb4d89e641abc1103

Change-Id: Idb0410a1946acbd7caf6a0bb1dad229bd5c2c346
(cherry picked from commit be2cc6a2)
(cherry picked from commit 698e909b)
(cherry picked from commit 81e55722)

In mysql 8.0.19 , Duplicate key error information is extended to
include the table name of the key.Previously, duplicate key error
information included only the key value and key name.

Unit tests are provided for updated changes.

Change-Id: Ic78059b625e73cece355541cb4d89e641abc1103
Closes-Bug: #1896916
(cherry picked from commit 2c2e6d48)
(cherry picked from commit b32b643a)
(cherry picked from commit 8867e335)

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.

Conflicts:
  .zuul.yaml

NOTE(stephenfin): Conflicts are due to different base jobs between
stable branches.

[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019390.html

Change-Id: Icd090cf8a36fa560bf7b0c67d0e1c4923c221c65
(cherry picked from commit a53ec14e)
(cherry picked from commit 1c0062c6)
(cherry picked from commit db2425f2)

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: Ie6891a40d3e90cc77ad15b7e4a6a36084399e9da

Change-Id: Iefdb36783bbb5e751589b965c83db3c3631a6ca8

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: I3e1e5ed4e72837d45b78e5ccb9ce8cca416e5c11
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>

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

blacklist:
 W504 line break after binary operator

Fix:
E305 expected 2 blank lines after class or function definition, found 1

Change-Id: I56d62f67914f07e7aef74f857c4b42e3bfd3416e

Nothing appears to be using this, based on codesearch.o.o, and it's
useless. Drop it.

Change-Id: I9ce39e69a6fdb2e216da9fd903b5dc8aa7eaab80
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Sem-Ver: api-break

No need for this in a Python 3-only world.

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

We don't need it anymore. Drop references to it.

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

Per [1], this is the latest supported version of SQLAlchemy. 1.1.x and
earlier are EOL.

[1] https://www.sqlalchemy.org/download.html#relstatus



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

Change-Id: Ic9424cf4e908edd794f2b7c1f6e3dd4316b6362c

Change-Id: I7bbab4f96391828d0b0e095a152bdacca6585e3c

Change-Id: I4245e31483865766c20443a79165f7d98bb5348a

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: I02e2d11d38d2aa4182e8d466519b99f05943701f

unittest2 was needed for Python versions <= 2.6, so it has not been
needed for quite some time now. See unittest2 note on:

https://docs.python.org/2.7/library/unittest.html



This drops unittest2 in favor of the standard unittest package.

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

move 'basepython' to the top-level 'testenv'

Change-Id: I37c608d9da6bffe2f24e0e1fbeb4e8d350089850

For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html

Change-Id: I68d368e2e1d3eb5f0fc608b79f242a6b680570e1

pbr has generated these for some time.

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

This is pretty ugly to look at, but essentially I've gone and replaced
all occurences of

  foo.bar(call_arg).AndReturn(return_arg)

with a mock of 'foo', followed by:

  mock_foo.return_value = return_arg

  <call>

  mock_foo.assert_call_once_with(call_arg)

Or 'side_effect'/'assert_has_calls' for functions that are called
multiple times.

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

Change-Id: Icb2c88dc18843cbf2f5be08d635d5ba10f36f360

SQLAlchemy 1.4 will be changing the method by which it
renders an IN expression such that the bound parameters
are not fully rendered until the statement is executed,
rather than when the statement is compiled into its initial
string form [1].   Adjust tests which are asserting the presence
of IN expressions based on the compiled form to allow for an
arbitrary expression within the parenthesis.

[1] https://github.com/sqlalchemy/sqlalchemy/issues/4645

Change-Id: I8640ad0cbd96647ed74678631479190146bd908e

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

Change-Id: I2c3a36fbc020d41c5eaa09008a0586142a63d6ba

Change-Id: I6ea68fb17ceac23337bfb7405eb3f7a6df8b61f2
Closes-Bug: 1851797

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: Idaca0bc97e33e0a080de612420177b5e102c628c

Change-Id: I57540c744ed6aa1edfea50b86d0900fdf59ceff9

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: I377ad03a73b88407d0e70315cbd0162bb9dc356b
Sem-Ver: feature

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: Ie47812bec5284d447a2f9c339a5b29d49d83ab53
Story: #2005924
Task: #34234