You can pass in a flag for a different storage device --> ./nova-volume --nodaemon --verbose --storage_dev=/dev/loop0 or in /etc/nova/nova-volume.conf: --storage_dev=/dev/loop0
Also, if you just make sure that the volume group already exists, it will work. The group should be called 'nova-volumes'. You can also specify a different volume group name with a flag --volume_group=vgfoo Vish On Wed, Aug 18, 2010 at 11:46 AM, Armando Migliaccio < [email protected]> wrote: > ** Description changed: > > I noticed that service.py under nova/volume contains this flag: > > flags.DEFINE_string('storage_dev', '/dev/sdb', 'Physical device to use > for volumes') > > my host does not have a /dev/sdb, so vgcreate in > _init_volume_group(self) fails and consequently lvcreate in _create_lv > fails too. It seems that no exeption is reported in the log file. > - Shouldn't storage_dev be /dev/loop0? > + Shouldn't storage_dev be /dev/loop0 or any other free loop device chosen > + by losetup? > > Thanks, > Armando > > ** Description changed: > > I noticed that service.py under nova/volume contains this flag: > > flags.DEFINE_string('storage_dev', '/dev/sdb', 'Physical device to use > for volumes') > > my host does not have a /dev/sdb, so vgcreate in > _init_volume_group(self) fails and consequently lvcreate in _create_lv > fails too. It seems that no exeption is reported in the log file. > Shouldn't storage_dev be /dev/loop0 or any other free loop device chosen > - by losetup? > + by losetup passed by $NOVA_VOLUME_ARGS? > > Thanks, > Armando > > -- > vgcreate/lvcreate in volume/service.py fail and go undetected > https://bugs.launchpad.net/bugs/620027 > You received this bug notification because you are a member of Nova > Bugs, which is subscribed to OpenStack Compute (nova). > > Status in OpenStack Compute (Nova): New > > Bug description: > I noticed that service.py under nova/volume contains this flag: > > flags.DEFINE_string('storage_dev', '/dev/sdb', 'Physical device to use for > volumes') > > my host does not have a /dev/sdb, so vgcreate in _init_volume_group(self) > fails and consequently lvcreate in _create_lv fails too. It seems that no > exeption is reported in the log file. Shouldn't storage_dev be /dev/loop0 or > any other free loop device chosen by losetup passed by $NOVA_VOLUME_ARGS? > > Thanks, > Armando > > > > > -- vgcreate/lvcreate in volume/service.py fail and go undetected https://bugs.launchpad.net/bugs/620027 You received this bug notification because you are a member of Registry Administrators, which is subscribed to OpenStack. _______________________________________________ Mailing list: https://launchpad.net/~registry Post to : [email protected] Unsubscribe : https://launchpad.net/~registry More help : https://help.launchpad.net/ListHelp
