FireEdge Sunstone cannot set deployment mode

[OpenNebulaSupport]

Description
When setting the Deployment Mode on a VM Template using FireEdge Sunstone. The parameter is ignored when submitting the XML issuing the one.template.update that follows

To Reproduce

• Update a VM Template
• Change Deployment Mode
  
• Save VM Template

ed Oct 23 03:51:44 2024 [Z0][ReM][D]: Req:6256 UID:0 IP:127.0.0.1 one.template.update invoked , 14, "<ROOT><ARCH>x86_64</ARCH><CPU>0.1</CPU><MEMORY>1024</MEMORY><HYPERVISOR>kvm</HYPERVISOR><CONTEXT><NETWORK>YES</NETWORK><SSH_PUBLIC_KEY>$USER[SSH_PUBLIC_KEY]</SSH_PUBLIC_KEY><START_SCRIPT>echo ok >/tmp/start_script</START_SCRIPT><TIMEZONE>Europe/Madrid</TIMEZONE><TOKEN>YES</TOKEN></CONTEXT><CPU_MODEL><MODEL>host-passthrough</MODEL></CPU_MODEL><GRAPHICS><LISTEN>0.0.0.0</LISTEN><TYPE>vnc</TYPE></GRAPHICS><NIC><NETWORK>public</NETWORK></NIC><NIC_DEFAULT><MODEL>virtio</MODEL></NIC_DEFAULT><OS><BOOT></BOOT></OS><SCHED_REQUIREMENTS>(HYPERVISOR=kvm)</SCHED_REQUIREMENTS></ROOT>", 0
Wed Oct 23 03:51:44 2024 [Z0][ReM][D]: Req:6256 UID:0 one.template.update result SUCCESS, 14

Expected behavior
Ruby Sunstone issues the API call correctly

Wed Oct 23 03:53:07 2024 [Z0][ReM][D]: Req:9872 UID:0 IP:127.0.0.1 one.template.update invoked , 14, "ARCH = "x86_64"
CONTEXT = [
  TIMEZONE = "Europe/Madrid",
  SSH_PUBLIC_KEY = "$USER[SSH_PUBLIC_KEY]",
  NETWORK = "YES",
  TOKEN = "YES",
  START_SCRIPT_BASE64 = "ZWNobyBvayA+L3RtcC9zdGFydF9zY3JpcHQ=" ]
CPU = "0.1"
CPU_MODEL = [
  MODEL = "host-passthrough" ]
GRAPHICS = [
  TYPE = "VNC",
  LISTEN = "0.0.0.0" ]
HYPERVISOR = "kvm"
MEMORY = "1024"
NIC = [
  NETWORK = "public" ]
NIC_DEFAULT = [
  MODEL = "virtio" ]
SCHED_REQUIREMENTS = "(HYPERVISOR=kvm)"
MEMORY_RESIZE_MODE = "BALLOONING"
MEMORY_UNIT_COST = "MB"
HOT_RESIZE = [
  CPU_HOT_ADD_ENABLED = "NO",
  MEMORY_HOT_ADD_ENABLED = "NO" ]
TM_MAD_SYSTEM = "ssh"
BACKUP_CONFIG = [
 ]
", 0
Wed Oct 23 03:53:07 2024 [Z0][ReM][D]: Req:9872 UID:0 one.template.update result SUCCESS, 14

Details

• Version: 6.10

Progress Status

• Code committed
• Testing - QA
• Documentation (Release notes - resolved issues, compatibility, known issues)