Bug 1710918

Summary:	Require updated microcode_ctl on hosts
Product:	[oVirt] ovirt-distribution	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	ovirt-host	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Novotny <pnovotny>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.3.3	CC:	bugs, didi, lleistne, mperina, sradco
Target Milestone:	ovirt-4.3.4	Flags:	sbonazzo: ovirt-4.3?
Target Release:	4.3.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-host-4.3.3-1	Doc Type:	Bug Fix
Doc Text:	ovirt-host now require a minimum version of microcode_ctl on x86_64 architecture ensuring to update it for addressing CVE-2018-12130, CVE-2018-12126, CVE-2018-12127, CVE-2019-11091	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-20 11:48:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1711224

Description Sandro Bonazzola 2019-05-16 14:49:29 UTC

On Fedora based oVirt Node microcode_ctl is missing and on EL7 host there is no strict requirement on minimum version for this package.
In order to ensure latest microcode is available on the host, requiring it here.
This should help with getting updates for CVE-2018-12130,
CVE-2018-12126, CVE-2018-12127, CVE-2019-11091.

Comment 1 Pavel Novotny 2019-06-14 13:14:31 UTC

Verified in ovirt-host-4.3.3-1.el7ev.x86_64

microcode_ctl >= 2.1-47.2 is now required for RHEL-based ovirt-host:

# rpm -q ovirt-host{,-dependencies}
ovirt-host-4.3.3-1.el7ev.x86_64
ovirt-host-dependencies-4.3.3-1.el7ev.x86_64
# rpm -qR ovirt-host-dependencies | grep microcode_ctl
microcode_ctl >= 2.1-47.2

Comment 2 Sandro Bonazzola 2019-06-20 11:48:03 UTC

This bugzilla is included in oVirt 4.3.4 release, published on June 11th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.4 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.