Bug 1653767

Summary: RHEL 7.6 - After yum update on overcloud, existing VM's are not starting [rhel-7.6.z]
Product: Red Hat Enterprise Linux 7 Reporter: Libor Miksik <lmiksik>
Component: tunedAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED ERRATA QA Contact: Tereza Cerna <tcerna>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.6CC: atelang, atragler, cfontain, fbaudin, jeder, jherrman, jraju, jskarvad, mburns, msuchane, olysonek, psklenar, salmy, supadhya, tcerna, toneata, yrachman, ysubrama
Target Milestone: rcKeywords: Triaged, Upstream, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: tuned-2.10.0-6.el7_6.3 Doc Type: If docs needed, set a value
Doc Text:
Previously, upgrading a Red Hat Enterprise Linux 7.5 node to Red Hat Enterprise Linux 7.6 in Red Hat OpenStack Plaform 10 caused virtual machines hosted on that node to become unable to start. This happened because a parameter was removed in the kvm_intel kernel module with updated kernel packages. With this update, Tuned rechecks supported module parameters, and the described problem no longer occurs.
Story Points: ---
Clone Of: 1649408 Environment:
Last Closed: 2019-03-13 18:44:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1649408    
Bug Blocks:    

Description Libor Miksik 2018-11-27 15:32:27 UTC
This bug has been copied from bug #1649408 and has been proposed to be backported to 7.6 z-stream (EUS).

Comment 3 Tereza Cerna 2019-01-21 08:59:28 UTC
Unfortunately, I was not able to reproduce this bug. -> Sanity only

Patch was applied in tuned version 2.10.0-6.el7_6.3 and looks well. Changes requested in primary bug was applied and no new errors appear, machine boots, kvm_intel module is enabled, content of /etc/modprobe.d/kvm.rt.tuned.conf is available.

Comment 7 errata-xmlrpc 2019-03-13 18:44:48 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-2019:0496