Bug 1609822
| Summary: | Rephrase: "command GetStatsAsyncVDS failed: Heartbeat exceeded" error message | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Piotr Kliczewski <pkliczew> |
| Component: | vdsm-jsonrpc-java | Assignee: | Piotr Kliczewski <pkliczew> |
| Status: | CLOSED ERRATA | QA Contact: | Pavol Brilla <pbrilla> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2.6 | CC: | lsurette, lsvaty, mperina, pkliczew, Rhev-m-bugs |
| Target Milestone: | ovirt-4.2.6 | Keywords: | Rebase, ZStream |
| 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: | 2018-09-04 13:41:18 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: | |||
|
Description
Piotr Kliczewski
2018-07-30 14:49:56 UTC
Verification steps? also bug mentioned in C1 is modified, is it intended? Heartbeat exceeded message [1] was updated. You can stop vdsm and see new message in the log. BZ #1552098 is upstream of this bug. [1] https://gerrit.ovirt.org/#/c/90844/1/client/src/main/java/org/ovirt/vdsm/jsonrpc/client/reactors/ReactorClient.java Error message found in logs:
/var/log/ovirt-engine/engine.log:2018-08-13 13:56:17,211+02 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [5fdb1676] Connection timeout for host '10.37.140.177', last response arrived 2254 ms ago.
/var/log/ovirt-engine/engine.log:2018-08-13 13:56:17,215+02 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Command 'SpmStatusVDSCommand(HostName = host, SpmStatusVDSCommandParameters:{hostId='cd5d7666-9beb-41f7-a66c-e5bc2b7adbaf', storagePoolId='fea9ecf6-9ed1-11e8-be09-001a4a013f0a'})' execution failed: VDSGenericException: VDSNetworkException: Connection timeout for host '10.37.140.177', last response arrived 2254 ms ago.
/var/log/ovirt-engine/engine.log:2018-08-13 13:56:37,943+02 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-65) [] Unable to RefreshCapabilities: ConnectException: Connection timeout
/var/log/ovirt-engine/engine.log:2018-08-13 13:56:37,949+02 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-65) [] Command 'GetCapabilitiesAsyncVDSCommand(HostName = host, VdsIdAndVdsVDSCommandParametersBase:{hostId='cd5d7666-9beb-41f7-a66c-e5bc2b7adbaf', vds='Host[host,cd5d7666-9beb-41f7-a66c-e5bc2b7adbaf]'})' execution failed: java.rmi.ConnectException: Connection timeout
/var/log/ovirt-engine/engine.log:2018-08-13 13:56:37,950+02 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-2) [] Command 'GetAllVmStatsVDSCommand(HostName = host, VdsIdVDSCommandParametersBase:{hostId='cd5d7666-9beb-41f7-a66c-e5bc2b7adbaf'})' execution failed: VDSGenericException: VDSNetworkException: Connection issue Connection timeout
/var/log/ovirt-engine/engine.log:2018-08-13 13:57:38,696+02 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [5fdb1676] Connection timeout for host '10.37.140.177', last response arrived 2002 ms ago.
/var/log/ovirt-engine/engine.log:2018-08-13 13:57:38,700+02 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-22) [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: VDSNetworkException: Connection timeout for host '10.37.140.177', last response arrived 2002 ms ago.
/var/log/ovirt-engine/engine.log:2018-08-13 13:57:41,566+02 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [5fdb1676] Connection timeout for host '10.37.140.177', last response arrived 2002 ms ago.
/var/log/ovirt-engine/engine.log:2018-08-13 13:57:41,570+02 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: VDSNetworkException: Connection timeout for host '10.37.140.177', last response arrived 2002 ms ago.
Verified on
# rpm -q ovirt-engine vdsm-jsonrpc-java
ovirt-engine-4.2.6.1_SNAPSHOT-89.g295078e.0.scratch.master.el7ev.noarch
vdsm-jsonrpc-java-1.4.14-1.el7ev.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2621 |