[astute] socket.shutdown fails when nothing connected
Bug #1290741 reported by
Andrey Danin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
Low
|
Vladimir Sharshov |
Bug Description
4.1
Problem is here: https:/
When timeout in line 110 has occured there is no client connected and socket.shutdown raises "Errno::ENOTCONN: Transport endpoint is not connected".
Maybe we should move socket.shutdown into Timeout clause or get git of it totally. And socket.close must be called only if socket is established.
Changed in fuel: | |
milestone: | none → 4.1.1 |
tags: | added: inprogress |
Changed in fuel: | |
milestone: | 4.1.1 → 5.1 |
Changed in fuel: | |
importance: | Medium → Low |
summary: |
- socket.shutdown fails when nothing connected + [astute] socket.shutdown fails when nothing connected |
Changed in fuel: | |
milestone: | 5.1 → 6.0 |
Changed in fuel: | |
milestone: | 6.0 → 6.1 |
tags: |
added: module-astute removed: astute inprogress mcagent |
Changed in fuel: | |
milestone: | 6.1 → 7.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/79872
Review: https:/