and let nova-volume create the group and the physical disk in one go. The command's output looks like below:
No physical volume label read from /dev/loop0
Physical volume "/dev/loop0" successfully created
Volume group "nova-volumes" successfully created
when I run nova-volume as daemon I finally get the volume group created!! I know it does not sound like a bug fix, but commenting pvcreate out does circumvent the problem.
If vgcreate takes care of the "pvcreation" too, would it make sense to have just one simple_execute call?
I commented out the pvcreate command under _init_volume_group
def _init_volume_ group(self) : simple_ execute( storage_ dev)) simple_ execute(
"sudo vgcreate %s %s" % (FLAGS. volume_ group,
FLAGS. storage_ dev))
if FLAGS.fake_storage:
return
#yield process.
# "sudo pvcreate %s" % (FLAGS.
yield process.
and let nova-volume create the group and the physical disk in one go. The command's output looks like below:
No physical volume label read from /dev/loop0
Physical volume "/dev/loop0" successfully created
Volume group "nova-volumes" successfully created
when I run nova-volume as daemon I finally get the volume group created!! I know it does not sound like a bug fix, but commenting pvcreate out does circumvent the problem.
If vgcreate takes care of the "pvcreation" too, would it make sense to have just one simple_execute call?