When testing out bug 586134 I found another issue and although similar to bug 517086 appears not to be the same issue.
If you create for example 200 1GB volumes like this:
for i in `seq 1 200` ; do euca-create-volume -z cluster1 -s 1 ; done
You will end up with quite a few failed. If you look in the logs it is usually caused by vgcreate failing for unknown reasons as the output of the command is not logged. If you run the same command on the command line that failed it will then work.
Also if you then delete all the volumes like this:
for i in `euca-describe-volumes | awk '{print $2}'` ; do euca-delete-volume $i ; done
You will end up with a huge number that do not get removed. If you look in the logs it is usually caused by lvremove failing for unknown reasons like with vgcreate. Again if you run the same command on the command line that failed it will then work.
When testing out bug 586134 I found another issue and although similar to bug 517086 appears not to be the same issue.
If you create for example 200 1GB volumes like this:
for i in `seq 1 200` ; do euca-create-volume -z cluster1 -s 1 ; done
You will end up with quite a few failed. If you look in the logs it is usually caused by vgcreate failing for unknown reasons as the output of the command is not logged. If you run the same command on the command line that failed it will then work.
Also if you then delete all the volumes like this:
for i in `euca-describe- volumes | awk '{print $2}'` ; do euca-delete-volume $i ; done
You will end up with a huge number that do not get removed. If you look in the logs it is usually caused by lvremove failing for unknown reasons like with vgcreate. Again if you run the same command on the command line that failed it will then work.
Chris