Description of problem: The parameter of the cinder driver volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver isn't configured in /etc/cinder/cinder.conf file. Version-Release number of selected component (if applicable): foreman-proxy-1.3.0-3.el6sat.noarch
@yrabl: What is the impact of this bug? Does it mean that via Foreman, Cinder can never work with LVM as the backend? Also, a bit confused. You have set the priority/severity to medium, but this is listed as a blocker. Those two settings I think are in conflict. If this bug implies that Foreman can never use Cinder with LVM, I would consider this bug to be High Priority vs. Medium. Please clarify. If this is indeed as I describe above, we can move this from RHOS 5.0 target to 4.0.z.
(In reply to Perry Myers from comment #2) The problem is that the Foreman doesn't configure the LVM driver automatically, and the user needs to configure the bug manually. Unlike Packstack, after the Foreman installation the user still needs to configure the Cinder's back end post installation. The priority is set for medium because it has a workaround (and there's plenty of documentation about it).
Ok, thanks for the clarification here. I agree that the bug is medium priority then, and that targeting RHOS 5.0 makes sense. I will remove the blocker flag though.
Is this something that we want staypuft/OFI to be doing on behalf of the user long term? Or should we leave that to the user to configure themselves?
(In reply to Mike Burns from comment #5) > Is this something that we want staypuft/OFI to be doing on behalf of the > user long term? Or should we leave that to the user to configure themselves? I see this as something we'll do with plugins/conf driven UI feature that Arthur is discussing
This bug was handled or obsoleted during the GA2 redesign work. If you believe that this still applies to the current UI, please re-open this bug.