UI does not send vApp properties when deploying VNF appliance with deploy-as-is template

[RosiKyu]

problem

When deploying a VNF appliance using a deploy-as-is template via the CloudStack UI, vApp properties configured in the deployment wizard are not included in the API request. The properties parameter is completely missing from the deployVnfAppliance API call, which results in failure to launch the appliance and it ends up in an Error state

(localcloud) 🐱 > listVirtualMachines id=a1593da3-fd58-494a-9e4e-977f8f24047c filter=id,name,details
{
  "count": 1,
  "virtualmachine": [
    {
      "details": {
        "Message.ReservedCapacityFreed.Flag": "false",
        "configurationId": "ASAv5",
        "cpuOvercommitRatio": "2.0",
        "dataDiskController": "osdefault",
        "deployvm": "true",
        "rootDiskController": "lsilogic"
      },
      "id": "a1593da3-fd58-494a-9e4e-977f8f24047c",
      "name": "vnf-ui-test3"
    }
  ]
}

versions

CloudStack: 4.20.3.0-SNAPSHOT
Browser: Chrome (Version 144.0.7559.59 (Official Build) (64-bit))

The steps to reproduce the bug

Steps to Reproduce

1. Register a deploy-as-is VNF template (e.g., Cisco ASAv OVA)
2. Navigate to Network → VNF Appliances → Add VNF Appliance
3. Select the deploy-as-is VNF template
4. Select compute offering and configure networks
5. In vApp properties section, configure required properties (e.g., set "Type Of Deployment" to "Standalone")
6. Accept license agreements and click Launch VNF Appliance
7. Observe the API request in browser Developer Tools (Network tab)

Expected Behavior

The API request should include the vApp properties parameter:
properties[0].key=HARole&properties[0].value=Standalone

Actual Behavior

The properties parameter is completely missing from the API request.

Example API call (note missing properties parameter):

http://10.0.34.148:8080/client/api/?zoneid=e9594751-da68-4f49-924f-222ba4c15876&dynamicscalingenabled=false&iothreadsenabled=false&templateid=88ac23d3-a3dd-4bcc-ab69-716a2b6c86dd&startvm=true&vnfconfiguremanagement=false&vnfcidrlist=0.0.0.0%2F0&serviceofferingid=b173ce1c-c52c-4617-9b8d-6dd8ea44afe1&details[0].configurationId=ASAv5&affinitygroupids=&nicnetworklist[0].nic=6&nicnetworklist[0].network=a170136d-9699-4586-8eaf-f83f19255a54&nicnetworklist[1].nic=9&nicnetworklist[1].network=fee6a3ae-b99f-4ebe-b84b-c661fc4d5888&nicnetworklist[2].nic=10&nicnetworklist[2].network=4935f651-04b5-49f7-b25a-55c6151ad5cb&nicnetworklist[3].nic=11&nicnetworklist[3].network=9427bebb-848d-4b54-8e22-06bfdcc83dcd&nicnetworklist[4].nic=12&nicnetworklist[4].network=9427bebb-848d-4b54-8e22-06bfdcc83dcd&nicnetworklist[5].nic=13&nicnetworklist[5].network=9427bebb-848d-4b54-8e22-06bfdcc83dcd&nicnetworklist[6].nic=14&nicnetworklist[6].network=9427bebb-848d-4b54-8e22-06bfdcc83dcd&nicnetworklist[7].nic=15&nicnetworklist[7].network=9427bebb-848d-4b54-8e22-06bfdcc83dcd&nicnetworklist[8].nic=16&nicnetworklist[8].network=9427bebb-848d-4b54-8e22-06bfdcc83dcd&nicnetworklist[9].nic=17&nicnetworklist[9].network=9427bebb-848d-4b54-8e22-06bfdcc83dcd&keypairs=&name=vnf-ui-test2&displayname=vnf-ui-test2&command=deployVnfAppliance&response=json&sessionkey=6Ed1jQk_Ip-qnwfOa8GaMuXyg2o

Only details[0].configurationId=ASAv5 is sent, but not the actual vApp property values: properties[0].key=HARole and properties[0].value=Standalone are NOT present.

Impact:

• VMs requiring OVF properties (like Cisco ASAv which requires HARole/Type of Deployment) fail to power on
• Error in vCenter: "Property 'Type of deployment' must be configured for the VM to power on"
• Users cannot deploy deploy-as-is VNF templates that have required OVF properties via UI

Related

This bug was discovered while testing PR #12499 (support deploy-as-is template as VNF template)
PR #12499 fixes the "VNF nics list is empty" error - that fix is working correctly. This is a separate UI bug affecting vApp properties serialization

Workaround Deployment via CloudMonkey CLI with the properties parameter works:

deployVnfAppliance templateid=<id> serviceofferingid=<id> zoneid=<id> nicnetworklist[0].nic=0 nicnetworklist[0].network=<network-id> name=vnf-test properties[0].key=HARole properties[0].value=Standalone

What to do about it?

No response

[weizhouapache]

thanks @RosiKyu
assigned to myself