Bug 1396308 - OSP-9/10 upgrades make blockstorage (LVM) nodes unusable and need workaround
Summary: OSP-9/10 upgrades make blockstorage (LVM) nodes unusable and need workaround
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 10.0 (Newton)
Assignee: Jiri Stransky
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On: 1393800
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-17 23:51 UTC by Don Domingo
Modified: 2016-11-17 23:58 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
When deploying or upgrading to a Red Hat OpenStack 10 environment that uses Ceph and dedicated blockstorage nodes for LVM, creating instances with attached volumes will no longer work. This is caused by a bug in the way the director configures the Block Storage service during upgrades. Specifically, the heat templates do not account by default for cases where Ceph and dedicated blockstorage nodes are configured together. As such, the director fails to define some required settings. Note that LVM is not a suitable Block Storage back end in production, particularly in enterprise environments. To work around this add an environment file to your upgrade/deployment that contains the following: parameter_defaults: BlockStorageExtraConfig: tripleo::profile::base::cinder::volume::cinder_enable_iscsi_backend: true tripleo::profile::base::cinder::volume::cinder_enable_rbd_backend: false
Clone Of: 1393800
Environment:
Last Closed: 2016-11-17 23:53:48 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1640730 0 None None None 2016-11-17 23:51:23 UTC

Comment 1 Don Domingo 2016-11-17 23:58:50 UTC
FYI: This issue is being fixed for OSP11 (https://bugs.launchpad.net/bugs/1640730).


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