|Summary:||[TestOnly] Make sure kernel bug 1516169 is included in 4.1.9|
|Product:||Red Hat Enterprise Virtualization Manager||Reporter:||Andrea Perotti <aperotti>|
|Component:||rhev-hypervisor-ng||Assignee:||Ryan Barry <rbarry>|
|Status:||CLOSED ERRATA||QA Contact:||cshao <cshao>|
|Version:||4.1.7||CC:||cshao, dfediuck, dguo, eedri, gklein, huzhao, mgoldboi, mkalinin, qiyuan, rbarry, sbonazzo, weiwang, yaniwang, ycui, yisong, yzhao|
|Target Milestone:||ovirt-4.1.9-1||Keywords:||TestOnly, ZStream|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2018-02-01 15:06:17 UTC||Type:||Bug|
|oVirt Team:||Node||RHEL 7.3 requirements from Atomic Host:|
Description Andrea Perotti 2017-11-22 23:06:04 UTC
Description of problem: There are those 2 kernel bugs#1516172 bugs#1516169 planned for next 7.4 batch release. We need to make sure it makes into 4.1.8 RHVH build since those bugs left hosts with no network. In case of link failure when NICs are member of an active standby bonding, the reaction of bonding is failed and system is left with NO ACTIVE interface, putting at risk the reliability of the hypervisors and of the whole infra. For further details check linked bz Opening this bug to make sure it is tracked and the customer(s) will be notified when 4.1.8 is out and ready to be consumed.
Comment 3 cshao 2018-01-16 03:16:20 UTC
Test version: redhat-virtualization-host-4.1-20180115.0 kernel-3.10.0-693.11.6.el7.x86_64 Test result: Current RHVH 4.1.9 didn't include the correct kernel version which mentioned in bug 1516169. So I will verify this bug once we include the correct one( > kernel-3.10.0-693.14.1.el7).
Comment 4 Huijuan Zhao 2018-01-26 03:10:53 UTC
Test version: redhat-virtualization-host-4.1-20180125.0 kernel-3.10.0-693.17.1.el7.x86_64 Test result: Current RHVH 4.1.9 includes the correct kernel version(kernel-3.10.0-693.17.1.el7.x86_64) So QE will verify this bug after its status is ON_QA.
Comment 6 cshao 2018-01-30 08:48:15 UTC
Verify this bug according #c4 & 5.
Comment 9 errata-xmlrpc 2018-02-01 15:06:17 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-2018:0263