Bug 1649408 - RHEL 7.6 - After yum update on overcloud, existing VM's are not starting
Summary: RHEL 7.6 - After yum update on overcloud, existing VM's are not starting
Status: ON_QA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tuned   
(Show other bugs)
Version: 7.6
Hardware: Unspecified
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: qe-baseos-daemons
Jiri Herrmann
URL:
Whiteboard:
Keywords: Triaged, Upstream, ZStream
Depends On:
Blocks: 1653819 1645412 1653767
TreeView+ depends on / blocked
 
Reported: 2018-11-13 15:09 UTC by yogananth subramanian
Modified: 2019-03-10 21:55 UTC (History)
15 users (show)

Fixed In Version: tuned-2.10.0-8.el7
Doc Type: Known Issue
Doc Text:
Upgrading a RHEL 7.5 node to RHEL 7.6 in RHOSP 10 breaks virtual machines on the node Currently, upgrading a Red Hat Enterprise Linux 7.5 node to Red Hat Enterprise Linux 7.6 in Red Hat OpenStack Plaform 10 causes virtual machines hosted on that node to become unable to start. To work around this problem, edit the `/etc/modprobe.d/kvm.rt.tuned.conf` file on the compute node, remove the following line, and reboot the node: options kvm_intel ple_gap=0 For this to work reliably, perform the changes before upgrading the node from RHEL 7.5 to RHEL 7.6.
Story Points: ---
Clone Of: 1645412
: 1653767 1653819 (view as bug list)
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Comment 1 Jaroslav Škarvada 2018-11-13 18:17:53 UTC
I am OK with the z-stream fix.

Comment 12 Jaroslav Škarvada 2018-11-22 16:45:41 UTC
Upstream commit addressing the problem:
https://github.com/redhat-performance/tuned/commit/c4a0aef63df41a79e96c1276ac732ecde8d58d86

It may look a bit over-engineered, but it's done this way to lower the possibility of race condition during Tuned startup / modules loading.


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