Deploying Cinder VMDK doesn't set up cinder-volume
Bug #1410517 reported by
Chris Clason
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Igor Gajsin | ||
5.1.x |
Fix Committed
|
High
|
Igor Gajsin | ||
6.0.x |
Fix Released
|
High
|
Igor Gajsin |
Bug Description
in 6.0, selecting cinder VMDK results in cinder-volume not being deployed on the controllers, instead it would require a node with the cinder role which would end up with an un-used storage volume.
affects: 6.1, 6.0, 5.1.x
Changed in fuel: | |
milestone: | none → 6.1 |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Andrew Woodward (xarses) |
description: | updated |
summary: |
- Puppet Scripts to Deploy VMDK Cinder Driver do not run + Deploying Cinder VMDK doesn't set up cinder-volume |
tags: | added: partner vcenter |
Changed in fuel: | |
assignee: | Andrew Woodward (xarses) → Bogdan Dobrelya (bogdando) |
Changed in fuel: | |
assignee: | Bogdan Dobrelya (bogdando) → Fuel Partner Integration Team (fuel-partner) |
Changed in fuel: | |
assignee: | Fuel Partner Integration Team (fuel-partner) → Igor Gajsin (igajsin) |
To post a comment you must log in.
Andrew, just assign cinder-role to controller node. In this case no useless storage volume will be used.