Bug 1112722
| Summary: | Vdsm's throws "xml-rpc handler exception" every 2 seconds in a case that it is up on one setup and non-responsive on an other setup | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Ori Gofen <ogofen> | ||||
| Component: | vdsm | Assignee: | Dan Kenigsberg <danken> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Gil Klein <gklein> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 3.5 | CC: | acanan, acathrow, amureini, bazulay, gklein, iheim, mgoldboi, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | infra | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-06-25 08:24:16 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Not sure we should support such a scenario, but in any event it's more of an infra issue than a storage one. Barak - up to you. This is not a bug. If your Vdsm becomes unresponsive, you *want* to know that someone else has taken over it. The other guy, who took your Vdsm, would rather know that someone still attempt to contact his newly-acquired host. This occasion is not expected to happen much, but when it does - it's quite bad (for the guy who lost his host). So extra logging is good. |
Created attachment 911778 [details] vdsm+engine logs Description of problem: An operation of adding a host to a setup while host is none-responsive on other setup results in success. after a few seconds vdsm throws an "xml-rpc handler exception": BindingXMLRPC::ERROR::2014-06-24 17:38:08,957::BindingXMLRPC::76::vds::(threaded_start) xml-rpc handler exception Traceback (most recent call last): File "/usr/share/vdsm/BindingXMLRPC.py", line 72, in threaded_start self.server.handle_request() File "/usr/lib64/python2.6/SocketServer.py", line 278, in handle_request self._handle_request_noblock() File "/usr/lib64/python2.6/SocketServer.py", line 288, in _handle_request_noblock request, client_address = self.get_request() File "/usr/lib64/python2.6/SocketServer.py", line 456, in get_request return self.socket.accept() File "/usr/lib64/python2.6/site-packages/vdsm/SecureXMLRPCServer.py", line 136, in accept raise SSL.SSLError("%s, client %s" % (e, address[0])) SSLError: sslv3 alert certificate unknown, client 10.35.161.37 and it keeps on doing so every few seconds thus flooding the log with ERRORS Version-Release number of selected component (if applicable): vdsm-4.15.0-78.git349f848.el6.x86_64 ovirt-engine-3.5.0-0.0.master.20140605145557.git3ddd2de.el6.noarch How reproducible: 100% Steps to Reproduce: Setup_1:dc + host Setup_2:uninitialized 1.Add an IP block from host to Setup_1's ovirt-engine,wait for host to be none-responsive 2.add the host to Setup_2 Actual results: vdsm throws "xml-rpc handler exception" every few seconds Expected results: vdsm should warn the user once in a reasonable time Additional info: