Bug 1349885

Summary: VDSNetworkException: Broken pipe
Product: [oVirt] ovirt-engine Reporter: jniederm
Component: BLL.InfraAssignee: Piotr Kliczewski <pkliczew>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: bugs, oourfali
Target Milestone: ovirt-4.1.0-alphaFlags: oourfali: ovirt-4.1?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
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: 2016-06-24 13:29:30 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:
Attachments:
Description Flags
condensed-engine.log
none
full-logs none

Description jniederm 2016-06-24 12:50:55 UTC
Created attachment 1171958 [details]
condensed-engine.log

Description of problem:
Recently I can often see following exception in engine log: 
Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: VDSGenericException: VDSNetworkException: Broken pipe
Most of the time (but not always) it is connected with failure of some VDSM related action. Steps to reproduce demos it on example of VM migration.

Version-Release number of selected component (if applicable):
4.1 master, commit 9c0d34d

How reproducible:
80%, not always

Steps to Reproduce:
1. Make sure there are at least 2 hosts Up in the cluster
2. Start vm
3. Migrate it

Actual results:
Migration fails, "VDSNetworkException: Broken pipe" in engine log

Expected results:


Additional info:

Comment 1 jniederm 2016-06-24 12:56:19 UTC
Created attachment 1171960 [details]
full-logs

Comment 2 jniederm 2016-06-24 13:01:59 UTC
vdsm version: 4.18.999-117.git46f735f.fc23

Comment 3 Oved Ourfali 2016-06-24 13:12:19 UTC
I suspect the migration failure is related to Bug 1349461.

Comment 4 Piotr Kliczewski 2016-06-24 13:29:30 UTC
Yes, this is the same issue.

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