Since we reenabled greendns with[1] nova functional test prints a warning at startup:
2022-07-08 11:03:40.374564 | ubuntu-focal | Modules with known eventlet monkey patching issues were imported prior to eventlet monkey patching: urllib3. This warning can usually be ignored if the caller is only importing and not executing nova code.
This is coming from [2]. It seems we think that urllib3 has monkey patching issues as reported in [3].
Based on tracing the imports eventlet import urllib3 for the greendns feature.
So I'm wondering if by reenabling greendns with [1] we actually reintroduced [3]. If yes, then we probably need to revert [1]. If not, then we probably remove urllib from our problems list in [2].
Since we reenabled greendns with[1] nova functional test prints a warning at startup:
2022-07-08 11:03:40.374564 | ubuntu-focal | Modules with known eventlet monkey patching issues were imported prior to eventlet monkey patching: urllib3. This warning can usually be ignored if the caller is only importing and not executing nova code.
This is coming from [2]. It seems we think that urllib3 has monkey patching issues as reported in [3].
Based on tracing the imports eventlet import urllib3 for the greendns feature.
So I'm wondering if by reenabling greendns with [1] we actually reintroduced [3]. If yes, then we probably need to revert [1]. If not, then we probably remove urllib from our problems list in [2].
[1]https:/ /review. opendev. org/c/openstack /nova/+ /830966 /github. com/openstack/ nova/blob/ 90c0c687a487601 e009c72f60c88be 92f6a55264/ nova/monkey_ patch.py# L76 /bugs.launchpad .net/nova/ +bug/1808951
[2]https:/
[3]https:/