Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1611968 (rhvm-setup-plugins-4.2.11) - Upgrade rhvm-setup-plugins to 4.2.11
Summary: Upgrade rhvm-setup-plugins to 4.2.11
Keywords:
Status: CLOSED ERRATA
Alias: rhvm-setup-plugins-4.2.11
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rhvm-setup-plugins
Version: 4.2.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.2.6
: ---
Assignee: Sandro Bonazzola
QA Contact: Pavol Brilla
URL:
Whiteboard:
Depends On: 1596152 1613471
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-03 07:39 UTC by Sandro Bonazzola
Modified: 2018-09-04 13:44 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Rebase: Enhancements Only
Doc Text:
Rebase package(s) to version: 4.2.11 This update removes the configuration parameter "CpuPinMigrationEnabled" from the vdc_options table in the database. With this update, live migration of High Performance virtual machines renders this configuration parameter unnecessary. (BZ#1457250)
Clone Of:
Environment:
Last Closed: 2018-09-04 13:44:08 UTC
oVirt Team: Virt
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:2627 None None None 2018-09-04 13:44:17 UTC

Description Sandro Bonazzola 2018-08-03 07:39:32 UTC
Rebase on 4.2.11

Comment 5 errata-xmlrpc 2018-09-04 13:44:08 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/RHEA-2018:2627


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