René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[BUG] UI: VNF NIC Mapping - Network select dropdown always disabled","articleBody":"### problem\n\nThe network selection dropdown in the VNF NIC Mappings step is permanently disabled, making it impossible to assign networks to NIC interfaces through the UI. VNF appliances can only be deployed via API/CLI as a workaround.\n\nRoot cause: In `ui/src/views/compute/wizard/VnfNicsSelection.vue` the `disabled` attribute is written as a plain HTML string instead of a Vue reactive binding (missing `:` prefix). In Vue/Ant Design, any non-empty string is treated as truthy — so the select is always disabled regardless of state. Additionally the logic is inverted: it disables the select when templateNics are present, which is exactly when the user needs to make a selection.\n\n### versions\n\nCloudStack: 4.22.1.0\nHypervisor: KVM (AlmaLinux)\nNetwork: Advanced networking\n\n### The steps to reproduce the bug\n\n1. Create an Isolated network (for WAN) and L2 network (for LAN)\n2. Go to Network → VNF Appliances → Add VNF Appliance\n3. Select a VNF template with NIC definitions\n4. Add networks on the Networks step\n5. Proceed to VNF NIC Mappings step\n6. All network dropdowns are disabled and cannot be clicked\n\n### What to do about it?\n\nRemove the `disabled` attribute from the a-select component in VnfNicsSelection.vue:\n\nBefore:\ndisabled=\"templateNics \u0026\u0026 templateNics.length \u003e 0\"\n\nAfter:\n(remove the line entirely)","author":{"url":"https://github.com/Gia-Bursulaia","@type":"Person","name":"Gia-Bursulaia"},"datePublished":"2026-06-05T18:59:57.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/13358/cloudstack/issues/13358"}