7a99462270
Recent dnspython release 2.0.0 (Jul 17, 2020) has caused ranger-agent-dbsync pod not to reach Completed state. When making a connection to the mariadb, a getaddrinfo call is made first which supposed to lookup the mariadb fqdn to ipaddress. The lookup failed which result in failed connection and retry indefinitely. As a result, ranger-agent-dbsync is stuck in Running state. This patch set provides a constraint to not use dnspython 2.2.0 version. Change-Id: I6e80772af70bbeff56024b585e378f7b3cafd945
26 lines
748 B
Plaintext
26 lines
748 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
#
|
|
pbr>=1.8
|
|
oslo.config>=5.2.0 # Apache-2.0
|
|
oslo.messaging>=5.29.0
|
|
oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0
|
|
oslo.db>=4.15.0
|
|
oslo.log>=3.36.0 # Apache-2.0
|
|
oslo.utils>=3.37.0 # Apache-2.0
|
|
dnspython>=1.15.0,!=2.0.0
|
|
pecan>=1.0.0,!=1.0.2,!=1.0.3,!=1.0.4
|
|
python-heatclient>=1.10.0 # Apache-2.0
|
|
python-glanceclient>=2.8.0 # Apache-2.0
|
|
python-keystoneclient>=3.8.0 # Apache-2.0
|
|
werkzeug>=0.11.5
|
|
eventlet>=0.24.1
|
|
SQLAlchemy<1.3.0,>=1.2.0
|
|
sqlalchemy-migrate>=0.11.0 # Apache-2.0
|
|
PyMySQL==0.9.3
|
|
lxml==4.3.2
|
|
PasteDeploy==2.0.1
|
|
psutil>=3.0.1
|
|
|