GitHub user akoskuczi-bw created a discussion: Guest network is created on wrong physical network when multiple physical networks exist
### problem When multiple physical networks are configured for guest traffic—one using VXLAN-based isolation and another using VLAN-based isolation—creating a new L2 guest network via the UI: Infrastructure -> Physical Networks -> Traffic Types -> Add Guest results in the network being created on the VXLAN-based physical network, regardless of the intended isolation type. ### versions 1. Hypervisor: KVM 2. Network setup: - Multiple physical networks for guest traffic - VXLAN + VLAN isolation types 3. KVM agent configuration: guest.network.device=broverlay ACS version: 4.22.0 OS: Ubuntu 24.04.3 LTS ### The steps to reproduce the bug 1. Configure two physical networks for guest traffic: - One with VXLAN-based isolation (kvmnetworklabel: broverlay) - One with VLAN-based isolation (kvmnetworklabel: brtrunk) 2. Ensure KVM hosts are configured with: guest.network.device=broverlay 3. Navigate to: Infrastructure -> Physical Networks -> Traffic Types -> Add Guest 4. Attempt to create a new L2 guest network with VLAN isolation **Expected result** The guest network should be created on the physical network from which the action was initiated (i.e., the selected VLAN-based physical network) **Actual result** The guest network is created on the VXLAN-based physical network, not on the selected one ### What to do about it? Using cmk, the VLAN-based guest network can be created successfully by explicitly specifying the physical network ID. Currently, the UI does not allow selecting the physical network when creating a guest network under Network -> Guest Networks; this option should be added. GitHub link: https://github.com/apache/cloudstack/discussions/12979 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
