You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
before upgrading to 5.6.1 from 5.4.13, when we did "onetemplate instantiate --name , the images from datastore 100 og linked to datastore 0, which both resides on the same nfs filesystem, shared by all hosts and servers in the setup.
After upgrading til 5.6.1, the images always get copied from datastore 100 to 0 when we instantiate, and then copied back, when we terminate the vm.
We have tried setting TM_MAD in the system datastore to "shared", but then the vm'es will not be deployed, stucked in pending.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. The OpenNebula Dev Team
This issue has been automatically closed due to lack of activity/feedback. Please reopen if you have further input or need to bump this. The OpenNebula Dev Team
Hi,
Vi have a system datastore (0):
ALLOW_ORPHANS="NO"
DS_MIGRATE="YES"
SHARED="NO"
TM_MAD="ssh"
TYPE="SYSTEM_DS"
and a file datastore (100):
CLONE_TARGET="SYSTEM"
DISK_TYPE="file"
DS_MAD="fs"
LN_TARGET="NONE"
TM_MAD="shared"
TYPE="IMAGE_DS"
before upgrading to 5.6.1 from 5.4.13, when we did "onetemplate instantiate --name , the images from datastore 100 og linked to datastore 0, which both resides on the same nfs filesystem, shared by all hosts and servers in the setup.
After upgrading til 5.6.1, the images always get copied from datastore 100 to 0 when we instantiate, and then copied back, when we terminate the vm.
We have tried setting TM_MAD in the system datastore to "shared", but then the vm'es will not be deployed, stucked in pending.
The text was updated successfully, but these errors were encountered: