Description of problem: The engine fails to fetch host statistics with "Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': '[Errno 22] Invalid argument'}]" an example is visible here: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-master/606/artifact/exported-artifacts/test_logs/he-basic-ansible-suite-master/post-012_local_maintenance_sdk.py/lago-he-basic-ansible-suite-master-engine/_var_log/ovirt-engine/engine.log No trace of that in vdsm logs. Version-Release number of selected component (if applicable): How reproducible: seen on CI Steps to Reproduce: 1. ? 2. 3. Actual results: an infinite loop of 2018-09-06 10:48:16,888-04 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-5) [] Unable to GetStats: VDSErrorException: VDSGenericException: VDSErrorException: Failed to Get Host Statistics, error = Internal JSON-RPC error: {'reason': '[Errno 22] Invalid argument'}, code = -32603 2018-09-06 10:48:25,066-04 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.GetStatsAsyncVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-11) [] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': '[Errno 22] Invalid argument'}] 2018-09-06 10:48:25,066-04 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetStatsAsyncVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-11) [] Failed in 'Get Host Statistics' method 2018-09-06 10:48:25,066-04 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.GetStatsAsyncVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-11) [] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': '[Errno 22] Invalid argument'}] Expected results: the engine correctly fetches host statistics Additional info:
Simone, is this error still reproduced? Unfortunately the original logs are no longer available and I can see in last 3 days HE suite finished successfully
(In reply to Martin Perina from comment #1) > Simone, is this error still reproduced? Unfortunately the original logs are > no longer available and I can see in last 3 days HE suite finished > successfully Yes, now it seams fine. Thanks.