Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 906796

Summary: engine doesn't poll vdsm host status after network error.
Product: [Retired] oVirt Reporter: Mark Wu <wudxw>
Component: ovirt-engine-coreAssignee: Nobody's working on this, feel free to take it <nobody>
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.2CC: acathrow, dyasny, iheim, ykaul
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: 2013-02-04 01:04:58 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:
Description Flags
engine.log none

Description Mark Wu 2013-02-01 14:03:47 UTC 
Description of problem:
If the host gets non-responsive because of a network error, then it can't get chance to come up. The setup just include one data center, one cluster and one host. The problematic host is SPM. I can't do any operation to recover it. I can run 'vdsClient -s 0 getVdsCaps' on host and login the vdsm host from engine. But I can't capture any network traffic target to vdsm host's 54321 port.

Version-Release number of selected component (if applicable):
ovirt-engine-3.2.0-2.fc18

How reproducible:
Sometimes.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Mark Wu 2013-02-01 14:04:49 UTC 
Created attachment 691591 [details]
engine.log
Comment 2 Itamar Heim 2013-02-03 12:47:24 UTC 
dup of 906795?
Comment 3 Mark Wu 2013-02-04 01:04:58 UTC 
Sorry,  I thought I didn't create it successfully.

*** This bug has been marked as a duplicate of bug 906795 ***