[SOLVED] Image is never placed in qcow2 system datastore after upgrade

Hello!

My VMs get never deployed to “qcow2” system datastore, it looks like Opennebula always consider “ssh” tranfer mode set.

I use network shared system datastore “100” (qcow2 type), and corresponding network shared qcow2 image datastore “101”.

I set SCHED_DS_REQUIREMENTS as “100” and expect that after VM deploy a link to disk image will be created in my system qcow2 datastore “100” as it was before (I use persistent image for my VM).

But when instatntiating VM the disk image is placed in local system datastore “0” in the Opennebula host where VM deployed to. That link is located in the directory with a name of VM id there.

Before upgrade everything was OK in 5.2 or maybe 5.4 version (I can’t remember it well). I didn’t change my datastores configs.

I met that problem first in 5.8.5, and to repair this I upgraded to 5.10 without success.

Yet I found that VM always has activated “ssh” transfer mode:
onevm show 515 | grep TM_MAD
TM_MAD_SYSTEM=“ssh”
but I did not activate it in the VM template.

To skip extra lines I have:
onevm show 515 -x

<TEMPLATE>
  <DISK>
    <DRIVER><![CDATA[qcow2]]></DRIVER>
    <TM_MAD_SYSTEM><![CDATA[ssh]]></TM_MAD_SYSTEM>
    <TYPE><![CDATA[FILE]]></TYPE>
  </DISK>
  <TM_MAD_SYSTEM><![CDATA[ssh]]></TM_MAD_SYSTEM>
</TEMPLATE>

To break this behaviour I tryed set
TM_MAD_SYSTEM=“qcow2”
in DISK section in VM template. No success.

More details:

onedatastore update 101
ALLOW_ORPHANS=“NO”
CLONE_TARGET=“SYSTEM”
CLONE_TARGET_SSH=“SYSTEM”
DISK_TYPE=“FILE”
DISK_TYPE_SSH=“FILE”
DRIVER=“qcow2”
DS_MAD=“fs”
LN_TARGET=“NONE”
LN_TARGET_SSH=“SYSTEM”
RESTRICTED_DIRS=“/”
SAFE_DIRS=“/lustre/cloud/datastores/backing.files/ /var/tmp/ /lustre/cloud/temp/”
TM_MAD=“qcow2”
TM_MAD_SYSTEM=“ssh”
TYPE=“IMAGE_DS”

onedatastore update 100
ALLOW_ORPHANS=“NO”
DISK_TYPE=“FILE”
DS_MIGRATE=“YES”
RESTRICTED_DIRS=“/”
SAFE_DIRS=“/var/tmp”
SHARED=“YES”
TM_MAD=“qcow2”
TYPE=“SYSTEM_DS”

extract from my oned.conf:
TM_MAD_CONF = [
NAME = “qcow2”, LN_TARGET = “NONE”, CLONE_TARGET = “SYSTEM”, SHARED = “YES”,
DS_MIGRATE = “YES”, TM_MAD_SYSTEM = “ssh”, LN_TARGET_SSH = “SYSTEM”,
CLONE_TARGET_SSH = “SYSTEM”, DISK_TYPE_SSH = “FILE”, DRIVER = “qcow2”

Could you, please, tell me the possible solutions to repair this?

with regards,
Dmitry

Solved! Since I have Opennebula+sunstone server installed in virtual environment, I rolled back to 5.2.1 and migrated to 5.10 one more time. It’s OK now.