Bug 1710818

Summary: Connection to host is stucked and host stays NonResponsive until engine restart
Product: Red Hat Enterprise Virtualization Manager Reporter: Martin Perina <mperina>
Component: vdsm-jsonrpc-javaAssignee: Piotr Kliczewski <pkliczew>
Status: CLOSED ERRATA QA Contact: Pavel Novotny <pnovotny>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.3.1CC: gveitmic, lleistne, lsurette, obockows, pkliczew, Rhev-m-bugs, sgoodman
Target Milestone: ovirt-4.3.5Keywords: Rebase, ZStream
Target Release: 4.3.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: vdsm-jsonrpc-java-1.4.18, ovirt-engine-4.3.5 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-12 11:53:06 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:
Bug Depends On:    
Bug Blocks: 1716327    

Description Martin Perina 2019-05-16 11:18:50 UTC 
Description of problem:

There are cases where host became NonResponsive due to networking or other issue, but even when it become reachable, engine is still considering it NonResponsive and only after restart of ovirt-engine service the communication between host and engine is restored again.


Version-Release number of selected component (if applicable):

rhvm-4.3.1.1-0.1.el7.noarch
vdsm-jsonrpc-java-1.4.15-2.el7ev.noarch

How reproducible:

?

Steps to Reproduce:

Unknown

Actual results:


Expected results:


Additional info:
Comment 9 Steve Goodman 2019-07-18 12:28:20 UTC 
It appears that this doesn't require any doc text. I'm setting the requires_doc_text field to "-". If this is incorrect, please let me know.
Comment 10 Piotr Kliczewski 2019-07-18 13:19:39 UTC 
It is correct, thank you!
Comment 11 Pavel Novotny 2019-07-24 21:53:37 UTC 
Verified in 
vdsm-jsonrpc-java-1.4.18-1.el7ev
ovirt-engine-4.3.5.4-0.1.el7.noarch

Having a running host (Up), I've cut the network connection. Host changed the status to NonResponsive.
After restoring the network connection, status changed back to Up.
I did several loops and the host status always went back tu Up.
Comment 13 errata-xmlrpc 2019-08-12 11:53:06 UTC 
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-2019:2428
Comment 14 Martin Perina 2019-08-21 06:01:39 UTC 
*** Bug 1726871 has been marked as a duplicate of this bug. ***
Comment 15 Daniel Gur 2019-08-28 13:11:24 UTC 
sync2jira
Comment 16 Daniel Gur 2019-08-28 13:15:35 UTC 
sync2jira