virt-who still uses xmlrpc requests to vdsm - https://github.com/virt-who/virt-who/blob/master/virtwho/virt/vdsm/vdsm.py#L125 In vdsm log you can see now: 2017-12-20 11:57:12,377+0200 INFO (Reactor thread) [ProtocolDetector.AcceptorImpl] Accepted connection from ::ffff:10.35.16.144:60842 (protocoldetector:61) 2017-12-20 11:57:12,389+0200 DEBUG (Reactor thread) [ProtocolDetector.Detector] Using required_size=11 (protocoldetector:89) 2017-12-20 11:57:12,390+0200 WARN (Reactor thread) [ProtocolDetector.Detector] Unrecognized protocol: 'POST /RPC2 ' (protocoldetector:132) 2017-12-20 11:57:12,390+0200 DEBUG (Reactor thread) [root] inside asyncore.dispatcher.close (asyncore:413) 2017-12-20 11:57:12,390+0200 DEBUG (Reactor thread) [root] deleting channel (asyncore:417) 2017-12-20 11:57:12,390+0200 DEBUG (Reactor thread) [root] deleting channel (asyncore:295) 2017-12-20 11:57:12,391+0200 DEBUG (Reactor thread) [root] closing socket (asyncore:420) This is new in 4.2, 4.1 vdsm still replies to such those requests. In #1353119 we already requested to use vdsm new client - https://github.com/oVirt/vdsm/blob/master/lib/vdsmclient/client.py
Hi Chris, As comment3, the VDSM API protocol is changed from vdsm-4.20, I'm afraid we need to change some virt-who functions for vdsm4.1x and 4.2x compatibility.
Hi Yaniv Bronhaim, rhev-4.2 is based on RHEL7.4 or 7.5? if 7.4, I think we should create a z-stream build for virt-who to fix the new API issue. if 7.5, the new API may be supported by virt-who when RHEL7.5 GA version is available.
(In reply to Eko from comment #5) > Hi Yaniv Bronhaim, > rhev-4.2 is based on RHEL7.4 or 7.5? > if 7.4, I think we should create a z-stream build for virt-who to fix the > new API issue. > if 7.5, the new API may be supported by virt-who when RHEL7.5 GA version is > available. Hi, unfortunately releases of RHV 4.2 GA and RHEL 7.5 are very close to each other, so we will need the fix to be included in both 7.4.z and 7.5. Thanks
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Moving to MODIFIED as virt-who has already been fixed: RHEL 7.4.z: - tracked by BZ1540296 - fixed in virt-who-0.19-8 RHEL 7.5: - tracked by BZ1353119 - fixed in virt-who-0.21.4-1
Based on above moving to ON_QA
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.