Bug 1349885 - VDSNetworkException: Broken pipe
Summary: VDSNetworkException: Broken pipe
Keywords:
Status: CLOSED DUPLICATE of bug 1349461
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.1.0-alpha
: ---
Assignee: Piotr Kliczewski
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-24 12:50 UTC by jniederm
Modified: 2016-06-24 13:29 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-06-24 13:29:30 UTC
oVirt Team: Infra
Embargoed:
oourfali: ovirt-4.1?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)
condensed-engine.log (41.43 KB, text/plain)
2016-06-24 12:50 UTC, jniederm
no flags Details
full-logs (673.37 KB, application/zip)
2016-06-24 12:56 UTC, jniederm
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.