René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"UI does not send vApp properties when deploying VNF appliance with deploy-as-is template","articleBody":"### problem\n\nWhen 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\n\n\u003cimg width=\"2000\" height=\"1060\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/1f681bf7-17fb-4ad8-8215-baa102115670\" /\u003e\n\n\u003cimg width=\"3188\" height=\"1666\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/31c12157-2d80-4713-a9cb-e1b3df60c41e\" /\u003e\n\n\u003cimg width=\"2592\" height=\"950\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/3d74c35b-2014-4e31-864d-46eb1ddffd06\" /\u003e\n\n```\n(localcloud) 🐱 \u003e listVirtualMachines id=a1593da3-fd58-494a-9e4e-977f8f24047c filter=id,name,details\n{\n  \"count\": 1,\n  \"virtualmachine\": [\n    {\n      \"details\": {\n        \"Message.ReservedCapacityFreed.Flag\": \"false\",\n        \"configurationId\": \"ASAv5\",\n        \"cpuOvercommitRatio\": \"2.0\",\n        \"dataDiskController\": \"osdefault\",\n        \"deployvm\": \"true\",\n        \"rootDiskController\": \"lsilogic\"\n      },\n      \"id\": \"a1593da3-fd58-494a-9e4e-977f8f24047c\",\n      \"name\": \"vnf-ui-test3\"\n    }\n  ]\n}\n```\n\n### versions\n\nCloudStack: 4.20.3.0-SNAPSHOT\nBrowser: Chrome (Version 144.0.7559.59 (Official Build) (64-bit))\n\n### The steps to reproduce the bug\n\nSteps to Reproduce\n\n1. Register a deploy-as-is VNF template (e.g., Cisco ASAv OVA)\n2. Navigate to Network → VNF Appliances → Add VNF Appliance\n3. Select the deploy-as-is VNF template\n4. Select compute offering and configure networks\n5. In vApp properties section, **configure required properties** (e.g., set \"Type Of Deployment\" to \"Standalone\")\n6. Accept license agreements and click Launch VNF Appliance\n7. Observe the API request in browser Developer Tools (Network tab)\n\n**Expected Behavior**\n\nThe API request should include the vApp properties parameter:\n`properties[0].key=HARole\u0026properties[0].value=Standalone`\n\n**Actual Behavior**\n\nThe properties parameter is completely missing from the API request.\n\nExample API call (note missing properties parameter):\n\n```\nhttp://10.0.34.148:8080/client/api/?zoneid=e9594751-da68-4f49-924f-222ba4c15876\u0026dynamicscalingenabled=false\u0026iothreadsenabled=false\u0026templateid=88ac23d3-a3dd-4bcc-ab69-716a2b6c86dd\u0026startvm=true\u0026vnfconfiguremanagement=false\u0026vnfcidrlist=0.0.0.0%2F0\u0026serviceofferingid=b173ce1c-c52c-4617-9b8d-6dd8ea44afe1\u0026details[0].configurationId=ASAv5\u0026affinitygroupids=\u0026nicnetworklist[0].nic=6\u0026nicnetworklist[0].network=a170136d-9699-4586-8eaf-f83f19255a54\u0026nicnetworklist[1].nic=9\u0026nicnetworklist[1].network=fee6a3ae-b99f-4ebe-b84b-c661fc4d5888\u0026nicnetworklist[2].nic=10\u0026nicnetworklist[2].network=4935f651-04b5-49f7-b25a-55c6151ad5cb\u0026nicnetworklist[3].nic=11\u0026nicnetworklist[3].network=9427bebb-848d-4b54-8e22-06bfdcc83dcd\u0026nicnetworklist[4].nic=12\u0026nicnetworklist[4].network=9427bebb-848d-4b54-8e22-06bfdcc83dcd\u0026nicnetworklist[5].nic=13\u0026nicnetworklist[5].network=9427bebb-848d-4b54-8e22-06bfdcc83dcd\u0026nicnetworklist[6].nic=14\u0026nicnetworklist[6].network=9427bebb-848d-4b54-8e22-06bfdcc83dcd\u0026nicnetworklist[7].nic=15\u0026nicnetworklist[7].network=9427bebb-848d-4b54-8e22-06bfdcc83dcd\u0026nicnetworklist[8].nic=16\u0026nicnetworklist[8].network=9427bebb-848d-4b54-8e22-06bfdcc83dcd\u0026nicnetworklist[9].nic=17\u0026nicnetworklist[9].network=9427bebb-848d-4b54-8e22-06bfdcc83dcd\u0026keypairs=\u0026name=vnf-ui-test2\u0026displayname=vnf-ui-test2\u0026command=deployVnfAppliance\u0026response=json\u0026sessionkey=6Ed1jQk_Ip-qnwfOa8GaMuXyg2o\n```\n\nOnly `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.\n\n**Impact:**\n\n- VMs requiring OVF properties (like Cisco ASAv which requires HARole/Type of Deployment) fail to power on\n- Error in vCenter: \"Property 'Type of deployment' must be configured for the VM to power on\"\n- Users cannot deploy deploy-as-is VNF templates that have required OVF properties via UI\n\n\u003cimg width=\"3103\" height=\"187\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/3b4d71fe-7298-4ddc-b36a-77b126a08fd8\" /\u003e\n\n**Related**\n\nThis bug was discovered while testing PR #12499 (support deploy-as-is template as VNF template)\nPR #12499 fixes the \"VNF nics list is empty\" error - that fix is working correctly. This is a separate UI bug affecting vApp properties serialization\n\n**Workaround** Deployment via CloudMonkey CLI with the properties parameter works:\n\n```\ndeployVnfAppliance templateid=\u003cid\u003e serviceofferingid=\u003cid\u003e zoneid=\u003cid\u003e nicnetworklist[0].nic=0 nicnetworklist[0].network=\u003cnetwork-id\u003e name=vnf-test properties[0].key=HARole properties[0].value=Standalone\n```\n\n\u003cimg width=\"2558\" height=\"855\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/850945ca-fecf-4b62-9032-d35c4c63d152\" /\u003e\n\n### What to do about it?\n\n_No response_","author":{"url":"https://github.com/RosiKyu","@type":"Person","name":"RosiKyu"},"datePublished":"2026-01-23T09:17:21.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/12510/cloudstack/issues/12510"}