If an external session object was not passed to the Session class, we
create a requests.Session() on our own. Once this is used, it may still
have an open connection when the auth Session is closed. We need to
handle the closing of the requests.Session() ourselves if we created
one. If you do not close it, a ResourceWarning may be reported about the
socket that is left open. If a session object is provided, we do not
attempt to close it as it will be up to the code consuming keystoneauth
to properly handle cleaning up the provided session.
Depends-On: https://review.opendev.org/757488
Change-Id: I590755d665b371c76ba8e02836d81d41a95ac601
Closes-Bug: #1838704
(cherry picked from commit b2b5ad3cb1
)
changes/11/760911/4
train-em
parent
7d7b9564ba
commit
8dc7366e76
@ -0,0 +1,9 @@
|
||||
---
|
||||
fixes:
|
||||
- >
|
||||
[`bug 1838704 <https://bugs.launchpad.net/keystone/+bug/1838704>`_]
|
||||
When consuming keystoneauth1.session.Session, if a requests session is not
|
||||
provided one is created. The Session used for requests may result in a
|
||||
ResourceWarning being generated if it is not properly closed. The code
|
||||
has been updated to close the session correctly when the Session object
|
||||
is deleted.
|
Loading…
Reference in new issue