Bug #1593

failed: mv: cannot remove /vmfs/volumes/*: Is a directory

Added by Giovanni Toraldo over 6 years ago. Updated over 6 years ago.

Status:ClosedStart date:10/25/2012
Priority:NormalDue date:
Assignee:Tino Vázquez% Done:

100%

Category:Drivers - Auth
Target version:Release 4.0
Resolution:fixed Pull request:
Affected Versions:OpenNebula 3.8

Description

After issuing a shutdown command to an instance using shared TM with a persistent image:

Thu Oct 25 16:24:55 2012 [LCM][I]: New VM state is SHUTDOWN
Thu Oct 25 16:25:10 2012 [VMM][E]: shutdown: Error executing: virsh -c 'esx://vmware001/?no_verify=1&auto_answer=1' --readonly dominfo one-45 err: ExitCode: 1
Thu Oct 25 16:25:10 2012 [VMM][I]: out:
Thu Oct 25 16:25:10 2012 [VMM][I]: error: failed to get domain 'one-45'
Thu Oct 25 16:25:10 2012 [VMM][I]: error: Domain not found: No domain with name 'one-45'
Thu Oct 25 16:25:10 2012 [VMM][I]: 
Thu Oct 25 16:25:10 2012 [VMM][I]: ExitCode: 0
Thu Oct 25 16:25:10 2012 [VMM][I]: Successfully execute virtualization driver operation: shutdown.
Thu Oct 25 16:25:10 2012 [VMM][I]: ExitCode: 0
Thu Oct 25 16:25:10 2012 [VMM][I]: Successfully execute network driver operation: clean.
Thu Oct 25 16:25:10 2012 [LCM][I]: New VM state is EPILOG
Thu Oct 25 16:25:10 2012 [TM][I]: Command execution fail: /srv/cloud/one/var/remotes/tm/shared/mvds vmware001:/vmfs/volumes/0/45/disk.0 /srv/cloud/one/var/datastores/1/facab93d8b58eadfa190a0cde6c704a8 45 1
Thu Oct 25 16:25:10 2012 [TM][I]: mvds: Moving /vmfs/volumes/0/45/disk.0 to datastore as /vmfs/volumes/1/facab93d8b58eadfa190a0cde6c704a8
Thu Oct 25 16:25:10 2012 [TM][E]: mvds: Command "umask 0007
Thu Oct 25 16:25:10 2012 [TM][I]: SRC_READLN=$(readlink -f /vmfs/volumes/0/45/disk.0)
Thu Oct 25 16:25:10 2012 [TM][I]: DST_READLN=$(readlink -f /vmfs/volumes/1/facab93d8b58eadfa190a0cde6c704a8)
Thu Oct 25 16:25:10 2012 [TM][I]: 
Thu Oct 25 16:25:10 2012 [TM][I]: if [ \( -L /vmfs/volumes/0/45/disk.0 \) -a \( "$SRC_READLN" = "$DST_READLN" \) ] ; then
Thu Oct 25 16:25:10 2012 [TM][I]: echo "Not moving files to image repo, they are the same" 
Thu Oct 25 16:25:10 2012 [TM][I]: else
Thu Oct 25 16:25:10 2012 [TM][I]: mv -f /vmfs/volumes/0/45/disk.0 /vmfs/volumes/1/facab93d8b58eadfa190a0cde6c704a8
Thu Oct 25 16:25:10 2012 [TM][I]: fi" failed: mv: cannot remove '/vmfs/volumes/1/facab93d8b58eadfa190a0cde6c704a8/disk.0': Is a directory
Thu Oct 25 16:25:10 2012 [TM][E]: Could not move image /vmfs/volumes/1/facab93d8b58eadfa190a0cde6c704a8
Thu Oct 25 16:25:10 2012 [TM][I]: ExitCode: 1
Thu Oct 25 16:25:10 2012 [TM][E]: Error executing image transfer script: Could not move image /vmfs/volumes/1/facab93d8b58eadfa190a0cde6c704a8
Thu Oct 25 16:25:10 2012 [DiM][I]: New VM state is FAILED

onevm show disk section:

DISK=[
  CLONE="NO",
  DATASTORE="default",
  DATASTORE_ID="1",
  DEV_PREFIX="hd",
  DISK_ID="0",
  IMAGE="ubuntu-vmdk",
  IMAGE_ID="4",
  PERSISTENT="YES",
  READONLY="NO",
  SAVE="YES",
  SOURCE="/srv/cloud/one/var/datastores/1/facab93d8b58eadfa190a0cde6c704a8",
  TARGET="hda",
  TM_MAD="shared",
  TYPE="FILE" ]

$ onedatastore list

  ID NAME                      CLUSTER         IMAGES TYPE     TM      
   0 system                    -                    0 -        shared  
   1 default                   -                    2 vmware   shared

Associated revisions

Revision 4f21b9ed
Added by Tino Vázquez over 6 years ago

Bug #1593: Fix for wrong treatment of persistent images in VMware shared configurations

Revision 0de7921c
Added by Tino Vázquez over 6 years ago

Bug #1593: Fix for wrong treatment of persistent images in VMware shared configurations
(cherry picked from commit 4f21b9ed312620864b5ee67fed053cccde67c7fd)

History

#1 Updated by Ruben S. Montero over 6 years ago

  • Description updated (diff)
  • Target version set to Release 4.0

#2 Updated by Tino Vázquez over 6 years ago

  • Status changed from New to Closed
  • Assignee set to Tino Vázquez
  • % Done changed from 0 to 100
  • Resolution set to fixed

Also available in: Atom PDF