Bug 1455203 - libvirt/hw_machine_type config option should be exposed
Summary: libvirt/hw_machine_type config option should be exposed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-nova
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: z4
: 10.0 (Newton)
Assignee: Ollie Walsh
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks: ospd_config_qemu_machine_type 1643032 1665040 1665041 1708565
TreeView+ depends on / blocked
 
Reported: 2017-05-24 13:10 UTC by Ollie Walsh
Modified: 2019-05-10 08:44 UTC (History)
6 users (show)

Fixed In Version: puppet-nova-9.5.4-2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-06 17:09:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 467587 0 None None None 2017-05-24 13:12:24 UTC
Red Hat Product Errata RHBA-2017:2654 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 10 director Bug Fix Advisory 2017-09-06 20:55:36 UTC

Description Ollie Walsh 2017-05-24 13:10:02 UTC 
The libvirt driver currently does not set the machine type for a KVM
guest by default.  When not specified, libvirt will use the newest
one it knows about.  Unfortunately, that can result in live
migrations failing if your environment is using different versions of
the host OS on compute nodes as the destination node may not be able
to support the machine type used when the VM was originally started.
Comment 1 Red Hat Bugzilla Rules Engine 2017-05-24 13:11:10 UTC 
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
Comment 5 errata-xmlrpc 2017-09-06 17:09:30 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-2017:2654
Note You need to log in before you can comment on or make changes to this bug.