It would be great to figure out why this is happening but ultimately It might be better if nova volume didn't go around creating volume groups at all and just checked to make sure the right one exists.
On Aug 19, 2010 9:35 AM, "Armando Migliaccio" <[email protected]> wrote: > by the way, with your changes I can see in the log that the pvcreate > call fails in the "if it already exists" case, but that (as you pointed > out) is not the problem here. It's just this oddity about the daemon > mode, which might potentially affect every other service! > > -- > 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
