The parameter 'target_ds' is required for this action


(Michael Luich) #1

I keep getting the following error:

The parameter ‘target_ds’ is required for this action.

I’m not understanding what I’m missing.

log:
Wed Oct 10 13:36:49 2018 [Z0][VM][I]: New state is ACTIVE
Wed Oct 10 13:36:49 2018 [Z0][VM][I]: New LCM state is PROLOG
Wed Oct 10 13:36:49 2018 [Z0][TM][I]: Command execution failed (exit code: 255): /var/lib/one/remotes/tm/vcenter/clone nebula.corp.actifio.com:one/17/AGM8.1.1-79-system.qcow2 wth05u27:/var/lib/one//datastores/0/9/disk.0 9 102
Wed Oct 10 13:36:49 2018 [Z0][TM][E]: The parameter ‘target_ds’ is required for this action.
Wed Oct 10 13:36:49 2018 [Z0][TM][E]: Error executing image transfer script: The parameter ‘target_ds’ is required for this action.
Wed Oct 10 13:36:49 2018 [Z0][VM][I]: New LCM state is PROLOG_FAILURE

Template:
TEMPLATE 16 INFORMATION
ID : 16
NAME : AGM8.1.1-79 NO Context
USER : oneadmin
GROUP : oneadmin
LOCK : None
REGISTER TIME : 10/10 13:13:04

PERMISSIONS
OWNER          : um-
GROUP          : ---
OTHER          : ---

TEMPLATE CONTENTS
CONTEXT=[
  NETWORK="YES",
  SSH_PUBLIC_KEY="$USER[SSH_PUBLIC_KEY]" ]
CPU="1"
DESCRIPTION="No Context"
DISK=[
  IMAGE="AGM8.1.1-79-NoContext",
  IMAGE_UNAME="oneadmin" ]
DISK=[
  DRIVER="qcow2",
  FORMAT="qcow2",
  SIZE="256000",
  TYPE="fs" ]
DISK=[
  DRIVER="qcow2",
  FORMAT="qcow2",
  SIZE="409600",
  TYPE="fs" ]
GRAPHICS=[
  LISTEN="0.0.0.0",
  TYPE="VNC" ]
HYPERVISOR="kvm"
INPUTS_ORDER=""
MEMORY="20480"
MEMORY_UNIT_COST="MB"
OS=[
  BOOT="disk0" ]
SCHED_REQUIREMENTS="HYPERVISOR=\"kvm\""
USER_INPUTS=[
  CPU="M|range-float||1..8|1",
  MEMORY="O|fixed|| |20480",
  VCPU="O|range||1..8|8" ]
VCPU="8"

vms/9/transfer.0.prolog
CLONE vcenter nebula.corp.actifio.com:one/17/AGM8.1.1-79-system.qcow2 wth05u27:/var/lib/one//datastores/0/9/disk.0 9 102
MKIMAGE ssh 256000 qcow2 wth05u27:/var/lib/one//datastores/0/9/disk.1 9 0
MKIMAGE ssh 409600 qcow2 wth05u27:/var/lib/one//datastores/0/9/disk.2 9 0

Any other helpful information I can provide?


(Michael Luich) #2

Okay a bit more digging.

for some reason the system is trying to use the vcenter driver to do the clone. This is not a vcenter instance … Why is it trying to use the vcenter driver?


(Michael Luich) #3

Well when you put the KVM image on the vCenter datastore you get this issue.
Are datastore’s not usable between the 2?