x/ranger-agent
Code Issues Proposed changes

Restrict dnspython to not use 2.0.0 version

Browse Source 
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
This commit is contained in:
Chi Lo 2020-07-23 20:27:57 +00:00
parent baf81a5641
commit 7a99462270
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
requirements.txt
View File

@ -9,6 +9,7 @@ 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