← Back to team overview

openstack team mailing list archive

[Cinder] Multi backend config issue

 

Hi Guys,

I'm running in a strange config issue with cinder-volume service.
I try to use the multi backend feature in grizzly and the scheduler
works fine but the volume service are not running correctly.
I can create/delete volumes but not attach.

My cinder.conf (abstract):
/
//#### Backend Configuration//
//scheduler_driver=cinder.scheduler.filter_scheduler.FilterScheduler//
//scheduler_host_manager=cinder.scheduler.host_manager.HostManager//
//
//enabled_backends=storage1,storage2//
//[storage1]//
//volume_group=nova-volumes//
//volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver//
//volume_backend_name=LVM_ISCSI//
//iscsi_helper=tgtadm//
//
//
//[storage2]//
//volume_group=nova-volumes//
//volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver//
//volume_backend_name=LVM_ISCSI//
//iscsi_helper=tgtadm/



this section is on each host the same. If i try to attach an existing
volume to an instance i'll get the following error on cinder-volume:

/2013-04-16 17:18:13    AUDIT [cinder.service] Starting cinder-volume
node (version 2013.1)//
//2013-04-16 17:18:13     INFO [cinder.volume.manager] Updating volume
status//
//2013-04-16 17:18:13     INFO [cinder.volume.iscsi] Creating
iscsi_target for: volume-b83ff42b-9a58-4bf9-8d95-945829d3ee9d//
//2013-04-16 17:18:13     INFO [cinder.openstack.common.rpc.common]
Connected to AMQP server on 10.0.0.104:5672//
//2013-04-16 17:18:13     INFO [cinder.openstack.common.rpc.common]
Connected to AMQP server on 10.0.0.104:5672//
//2013-04-16 17:18:14     INFO [cinder.volume.manager] Updating volume
status//
//2013-04-16 17:18:14     INFO [cinder.openstack.common.rpc.common]
Connected to AMQP server on 10.0.0.104:5672//
//2013-04-16 17:18:14     INFO [cinder.openstack.common.rpc.common]
Connected to AMQP server on 10.0.0.104:5672//
//2013-04-16 17:18:26    ERROR [cinder.openstack.common.rpc.amqp]
Exception during message handling//
//Traceback (most recent call last)://
//  File
"/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/amqp.py",
line 430, in _process_data//
//    rval = self.proxy.dispatch(ctxt, version, method, **args)//
//  File
"/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/dispatcher.py",
line 133, in dispatch//
//    return getattr(proxyobj, method)(ctxt, **kwargs)//
//  File "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py",
line 665, in initialize_connection//
//    return self.driver.initialize_connection(volume_ref, connector)//
//  File "/usr/lib/python2.7/dist-packages/cinder/volume/driver.py",
line 336, in initialize_connection//
//    if self.configuration.iscsi_helper == 'lioadm'://
//  File
"/usr/lib/python2.7/dist-packages/cinder/volume/configuration.py", line
83, in __getattr__//
//    return getattr(self.local_conf, value)//
//  File "/usr/lib/python2.7/dist-packages/oslo/config/cfg.py", line
1708, in __getattr__//
//    return self._conf._get(name, self._group)//
//  File "/usr/lib/python2.7/dist-packages/oslo/config/cfg.py", line
1513, in _get//
//    value = self._substitute(self._do_get(name, group))//
//  File "/usr/lib/python2.7/dist-packages/oslo/config/cfg.py", line
1529, in _do_get//
//    info = self._get_opt_info(name, group)//
//  File "/usr/lib/python2.7/dist-packages/oslo/config/cfg.py", line
1629, in _get_opt_info//
//    raise NoSuchOptError(opt_name, group)//
//NoSuchOptError: no such option in group storage1: iscsi_helper/


It's very strange the
'/volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver//'/ option
should set the iscsi_helper=tgtadm per default.


Anyone have an idea or the same issue, otherwise i'll create a bug report.

Greetings from Berlin
Heiko

Follow ups