Can not close socket when abnormal termination in Notification process.
Bug #1911124 reported by
Wataru Juso
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tacker |
Fix Released
|
Medium
|
Wataru Juso | ||
Bug Description
# Problem & Affected
When sending notifications, the API is sent using requests.session.
Currently, no timeout value is set. Therefore, if there is no response
from the connected server, it will not be able to close its own socket
even if it terminates abnormally.
# Expected behavior:
For solving this problem, add vnf_lcm.timeout to tacker.conf.
When submitting the API, the timeout value is set to the requests api.
I think that default value is 60seconds.
| Changed in tacker: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Wataru Juso (w-juso) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/tacker 5.0.0.0rc1 | #1 |
Revision history for this message
| Yasufumi Ogawa (yasufum) wrote | #2 |
| Changed in tacker: | |
| status: | New → Fix Released |
To post a comment you must log in.
This issue was fixed in the openstack/tacker 5.0.0.0rc1 release candidate.