Bug #4944

tm/shared/clone: ceph disk clone is failing with shared system ds

Added by Laurent Grawet almost 4 years ago. Updated over 3 years ago.

Status:ClosedStart date:11/29/2016
Priority:HighDue date:
Assignee:-% Done:

0%

Category:Drivers - Storage
Target version:Release 5.4
Resolution:invalid Pull request:
Affected Versions:OpenNebula 5.2

Description

Hi,

This is related to Bug #4924.
I work with a shared system DS (nfs)
I've configured ceph as DS_MAD=ceph and TM_MAD=shared

The problem arise during vm startup, when non persistent ceph disk should be cloned.
/var/lib/one/remotes/tm/shared/clone script is called and there is specific qcow code, starting at line 90, which should not be executed.

#-------------------------------------------------------------------------------
# Clone (cp) SRC into DST
#-------------------------------------------------------------------------------

if [ -n "$ORIGINAL_SIZE" -a "$SIZE" -gt "$ORIGINAL_SIZE" ]; then
   RESIZE_CMD="; qemu-img resize ${DST_PATH} ${SIZE}M" 
fi

log "Cloning $SRC_PATH in $DST" 

CLONE_CMD="cd ${DST_DIR}; \
    rm -f ${DST_PATH}; \
    cp ${SRC_PATH} ${DST_PATH} \
    ${RESIZE_CMD}" 

ssh_exec_and_log $DST_HOST \
                 "$CLONE_CMD" \
                 "Error copying $SRC to $DST" 

Also, /var/lib/one/remotes/tm/ceph/clone is never called and ceph disk is not cloned.

Thanks for your help,

Laurent

History

#1 Updated by Laurent Grawet over 3 years ago

#2 Updated by Vlastimil Holer over 3 years ago

  • Status changed from Pending to Closed
  • Resolution set to invalid

Hello,

you are using wrong settings for the datastores.

Laurent Grawet wrote:

Hi,

This is related to Bug #4924.
I work with a shared system DS (nfs)

system DS with TM_MAD=shared is OK.

I've configured ceph as DS_MAD=ceph and TM_MAD=shared

The image DS must be DS_MAD=ceph, TM_MAD=ceph.

But, there is still bug in current stable packages, which breaks the live migrations on Ceph with shared filesystem. Simple PR 160 referenced from bug #4924 must be applied. Patch is already merged in master and 5.2 branch (in case there is a bugfix release for 5.2).

Also, the documentation is going to be updated to more clearly describe what are the TM_MAD options for each DS.

Because this bug was created on unsupported DS (TM_MAD) configuration, I'm closing it as invalid.

Thank you for the report.

Best regards,
Vlastimil Holer

Also available in: Atom PDF