Bug 1414075
| Summary: | Support for 0.25 m2crypto (on Fedora) | ||
|---|---|---|---|
| Product: | [oVirt] vdsm | Reporter: | Piotr Kliczewski <pkliczew> |
| Component: | Bindings-API | Assignee: | Piotr Kliczewski <pkliczew> |
| Status: | CLOSED NOTABUG | QA Contact: | Lukas Svaty <lsvaty> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.20.0 | CC: | bugs, lsvaty, mperina, pkliczew |
| Target Milestone: | ovirt-4.2.0 | Flags: | rule-engine:
ovirt-4.2+
lsvaty: testing_ack+ |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-06-23 08:26:52 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Moving to 4.2 for now. When/if we start building oVirt 4.1 for FC25 officially, we can retarget. Piotr, are we really using m2crypto on master? didn't we remove it from vdsm? If so, please close wontfix or change summary. We are not using it anymore. Closing as NOTABUG as we removed m2crypto from VDSM in the meantime |
I tested vdsm 4.20.0-228.git4739c81 on f25 and noticed that engine nor mom is not able to connect due to vdsm: I see 2017-01-17 17:49:53,826 ERROR (Reactor thread) [vds.dispatcher] uncaptured python exception, closing channel <yajsonrpc.betterAsyncore.Dispatcher ('::ffff:192.168.1.105', 39378, 0, 0) at 0x7fdc180d6ab8> (<type 'exceptions.TypeError'>:an integer is required [/usr/lib64/python2.7/asyncore.py|readwrite|108] [/usr/lib64/python2.7/asyncore.py|handle_read_event|449] [/usr/lib/python2.7/site-packages/yajsonrpc/betterAsyncore.py|handle_read|67] [/usr/lib/python2.7/site-packages/yajsonrpc/betterAsyncore.py|_delegate_call|149] [/usr/lib/python2.7/site-packages/vdsm/protocoldetector.py|handle_read|142] [/usr/lib/python2.7/site-packages/yajsonrpc/stompreactor.py|handle_socket|487] [/usr/lib/python2.7/site-packages/vdsm/rpc/bindingjsonrpc.py|add_socket|49] [/usr/lib/python2.7/site-packages/yajsonrpc/stompreactor.py|createListener|454] [/usr/lib/python2.7/site-packages/yajsonrpc/stompreactor.py|StompListener|420] [/usr/lib/python2.7/site-packages/yajsonrpc/betterAsyncore.py|__init__|43] [/usr/lib/python2.7/site-packages/yajsonrpc/betterAsyncore.py|switch_implementation|82] [/usr/lib/python2.7/site-packages/yajsonrpc/stompreactor.py|init|435] [/usr/lib64/python2.7/asyncore.py|set_reuse_addr|313] [/usr/lib64/python2.7/site-packages/M2Crypto/SSL/Connection.py|getsockopt|414] [/usr/lib64/python2.7/socket.py|meth|228]) (betterAsyncore:160) which changes to infinitive loop: 2017-01-17 17:50:24,093 WARN (JsonRpc (StompReactor)) [vds.dispatcher] unhandled read event (betterAsyncore:160) 2017-01-17 17:50:24,093 WARN (JsonRpc (StompReactor)) [vds.dispatcher] unhandled read event (betterAsyncore:160) 2017-01-17 17:50:24,093 WARN (JsonRpc (StompReactor)) [vds.dispatcher] unhandled read event (betterAsyncore:160) 2017-01-17 17:50:24,093 WARN (JsonRpc (StompReactor)) [vds.dispatcher] unhandled read event (betterAsyncore:160) 2017-01-17 17:50:24,093 WARN (JsonRpc (StompReactor)) [vds.dispatcher] unhandled read event (betterAsyncore:160) 2017-01-17 17:50:24,093 WARN (JsonRpc (StompReactor)) [vds.dispatcher] unhandled read event (betterAsyncore:160) 2017-01-17 17:50:24,093 WARN (JsonRpc (StompReactor)) [vds.dispatcher] unhandled read event (betterAsyncore:160) 2017-01-17 17:50:24,093 WARN (JsonRpc (StompReactor)) [vds.dispatcher] unhandled read event (betterAsyncore:160) 2017-01-17 17:50:24,093 WARN (JsonRpc (StompReactor)) [vds.dispatcher] unhandled read event (betterAsyncore:160) We need to make sure that vdsm is able to use newer version of m2crypto: Name : m2crypto Arch : x86_64 Epoch : 0 Version : 0.25.1 Release : 1.fc25