[Bug 590929] [NEW] eucalyptus create and delete volumes sometimes fail on lvm commands

[Chris Cheney]

Public bug reported:

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.

Also despite the failure to properly delete the volume euca-describe-
volumes will have invalid information. For example if you delete the
volume it will no longer show up in the list but it will still be there
as seen by losetup and vgscan, and will still be set back up by
eucalyptus when rebooted but it will not show up in the euca-describe-
volume list.

Chris

** Affects: eucalyptus (Ubuntu)
     Importance: Medium
         Status: Confirmed

** Affects: eucalyptus (Ubuntu Lucid)
     Importance: Medium
         Status: Confirmed

** Description changed:

  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.
  
+ Also despite the failure to properly delete the volume euca-describe-
+ volumes will have invalid information. For example if you delete the
+ volume it will no longer show up in the list but it will still be there
+ as seen by losetup and vgscan, and will still be set back up when
+ rebooted by eucalyptus but it will not show up in the euca-describe-
+ volume list.
+ 
  Chris

** Description changed:

  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.
  
  Also despite the failure to properly delete the volume euca-describe-
  volumes will have invalid information. For example if you delete the
  volume it will no longer show up in the list but it will still be there
- as seen by losetup and vgscan, and will still be set back up when
- rebooted by eucalyptus but it will not show up in the euca-describe-
+ as seen by losetup and vgscan, and will still be set back up by
+ eucalyptus when rebooted but it will not show up in the euca-describe-
  volume list.
  
  Chris

-- 
eucalyptus create and delete volumes sometimes fail on lvm commands
https://bugs.launchpad.net/bugs/590929
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.