Bug 1328147 - instack-virt-setup configures "unsafe" disk caching
Summary: instack-virt-setup configures "unsafe" disk caching
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Angus Thomas
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-18 15:04 UTC by Brent Eagles
Modified: 2017-01-27 22:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-27 22:59:18 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1570042 0 None None None 2016-04-18 15:09:00 UTC

Description Brent Eagles 2016-04-18 15:04:34 UTC 
When using instack-virt-setup, the libvirt domains are configured with the "unsafe" cache mode. This increase the risk of corrupting the undercloud and baremetal VMs in the event of power failure or unclean shutdown of VMs (e.g. force resets from the virt-manager GUI, etc).

Removing the cache option to and just using the libvirt/qemu defaults is probably preferable.
Note You need to log in before you can comment on or make changes to this bug.