Bug 1410848

Summary: [TestOnly] RHV-H 7.3 susceptible to kernel BZ 1404060
Product: Red Hat Enterprise Virtualization Manager Reporter: Gordon Watson <gwatson>
Component: ovirt-node-ngAssignee: Ryan Barry <rbarry>
Status: CLOSED ERRATA QA Contact: cshao <cshao>
Severity: high Docs Contact:
Priority: high    
Version: 4.0.5CC: cshao, dfediuck, gklein, gwatson, lsurette, mgoldboi, mkalinin, rbarry, ycui, ykaul
Target Milestone: ovirt-4.0.7Keywords: Rebase, TestOnly, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Fixed In Version: redhat-virtualization-host-4.0-20170302.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-16 15:39:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1404060    
Bug Blocks:    

Description Gordon Watson 2017-01-06 15:47:25 UTC
Description of problem:

There is a RHEL 7.3 kernel bug, BZ 1404060, that causes VM migrations to fail between hosts that use Intel X710 NICs.

RHV-H 7.3 is susceptible to this bug.

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

- RHV-4 7.3
- redhat-release-virtualization-host-4.0-5.2.el7.x86_64

How reproducible:

If Intel X710 NICs used for the VM migrations, they will most likely fail at least within a few attempts. 

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 7 cshao 2017-02-21 10:44:28 UTC
Move back to modify status due to there is no 4.0.7 build available for testing.

Comment 8 cshao 2017-02-23 10:42:53 UTC
Test version:

Test result:
# rpm -qa| grep kernel

RHVH should include kernel-3.10.0-514.10.2.el7, so change bug status to ASSIGNED.

Comment 13 cshao 2017-03-03 05:10:33 UTC
Test version:

Test result:
# rpm -qa| grep kernel

Test result:
RHVH include the correct kernel, so the bug is fixed, change bug status to VERIFY.

Comment 17 errata-xmlrpc 2017-03-16 15:39:25 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.