From 7577743d00aa50da768b2fa562290abbdee0acb7 Mon Sep 17 00:00:00 2001
From: Rodolfo Alonso Hernandez <ralonsoh@redhat.com>
Date: Tue, 25 May 2021 11:43:35 +0000
Subject: [PATCH] Block alembic 1.6.3

As described in [1], since #844 was introduced, when a table is
created, all columns "index" and "unique" flags are unset.

In 1.6.4 [2], "CreateTableOp" sets the flag
"_constraints_included" to False by default. That will honor
the "index" and "unique" flags set in each column definition.

Related-Bug: #1929518

[1]https://github.com/sqlalchemy/alembic/issues/848
[2]https://gerrit.sqlalchemy.org/c/sqlalchemy/alembic/+/2839

Change-Id: I90380b027cade633088099ae766ff5c116014cea
---
 global-requirements.txt | 2 +-
 upper-constraints.txt   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/global-requirements.txt b/global-requirements.txt
index c5fff8282a..2af645d6b3 100644
--- a/global-requirements.txt
+++ b/global-requirements.txt
@@ -1,5 +1,5 @@
 abclient  # Apache-2.0
-alembic!=1.2.0  # MIT
+alembic!=1.2.0,!=1.6.3  # MIT
 amqp!=2.1.4,!=5.0.4  # BSD
 ansible-runner!=1.3.5  # Apache 2.0
 anyjson  # BSD
diff --git a/upper-constraints.txt b/upper-constraints.txt
index cb335aacb9..d81240601e 100644
--- a/upper-constraints.txt
+++ b/upper-constraints.txt
@@ -534,7 +534,7 @@ futurist===2.3.0
 jsonschema===3.2.0
 sphinxcontrib-devhelp===1.0.2
 python-blazarclient===3.2.0
-alembic===1.6.3
+alembic===1.6.2
 execnet===1.8.0
 glance-store===2.5.0
 sphinxcontrib-programoutput===0.17