You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ISO deploy causes unwanted isolated guest network creation even when L2 network is selected #11227
When deploying a VM using an ISO image, CloudStack automatically creates an isolated guest network using the default offering DefaultIsolatedNetworkOfferingWithSourceNatService — even though an L2 network is explicitly selected during deployment.
In a clean system, this behavior doesn't happen and the selected L2 network is honored without creating a new one.
After comparing the configurations of two identical CloudStack environments (one working, one problematic), we found extra or differing entries in network_offering_details — particularly involving parameters like internetProtocol, domainid, etc.
This seems to trigger the system into thinking it needs a network with DHCP capabilities, which leads to the automatic L3 network creation.
versions
CloudStack version: 4.20.1.0
Hypervisor: VMware
The steps to reproduce the bug
Log in to the CloudStack UI.
Navigate to “ISO” and register or select an existing ISO image (e.g., Ubuntu 20.04 or Windows Server 2022).
Go to “Instances” and click “Deploy VM”.
Select a custom offering, disk offering, and in the Network step, choose an existing L2 Guest Network (not isolated).
Complete the wizard and click “Launch VM”.
Observe that CloudStack automatically creates an Isolated Guest Network (L3) using the offering DefaultIsolatedNetworkOfferingWithSourceNatService.
The VM NIC is attached to the newly created L3 network instead of the selected L2 network.
i have also seen this issue where I selected L2 network but an isolated network was created after the instance was deployed and the instance was attached to the isolated network rather than the desired L2 network. At the time, my testing was limited but it seemed to be related to a template being present within the system that had the same OS type as the instance i deployed (I am not quite sure if this was the true cause). I will need to test the ISO method you mentioned above.
Activity
kiranchavala commentedon Jul 23, 2025
@omurozlu Not able to reproduce the issue
Could you please provide the management server logs to investigate further
mattmonday88 commentedon Jul 29, 2025
i have also seen this issue where I selected L2 network but an isolated network was created after the instance was deployed and the instance was attached to the isolated network rather than the desired L2 network. At the time, my testing was limited but it seemed to be related to a template being present within the system that had the same OS type as the instance i deployed (I am not quite sure if this was the true cause). I will need to test the ISO method you mentioned above.
omurozlu commentedon Jul 30, 2025
@kiranchavala
management server log.
@mattmonday88 I get this error when I create a machine with the iso
kiranchavala commentedon Aug 4, 2025
@omurozlu I tried a vm deployment with an iso and used custom compute offering and disk offering , but couldn't reproduce the issue.
Do you have screen recording that you can share?
weizhouapache commentedon Aug 20, 2025
@omurozlu
full logs of job
job-46562?maybe networkid/networkids are not passed in the deployvirtualmachine API