problem
Error Unable to convert network offering with specified id to network profile with
cmk create network name="L2 Guest No VLAN" displaytext="L2 Guest SVA" zoneid=$ZONE_ID networkofferingid=$NETOFF_ID physicalnetworkid=$PHNET_ID
Not possible to define the L2 guest network without VLAN.
versions
CloudStack 4.20.1.0
Ubuntu 24.04.2
Bridge configuration:
cloud0 8000.76c30d2f0eda no vnet0
vnet1
cloudbr0 8000.aa2581097bfd no eno3
vnet2
vnet3
vnet4
vnet5
cloudbr1 8000.86803b4ff344 no eno2
cloudbr2 8000.6af97cf2fcad no eno1
The steps to reproduce the bug
debug-error.txt
- updateZone - ok
- create physicalnetwork - ok
- add traffictype - ok
- update physicalnetwork - ok
- create networkoffering - ok
- update networkoffering - ok
- updateZone -ok
- create network - Unable to convert network offering with specified id to network profile
export ZONE_ID=e4a7648a-2847-446d-b6da-43d6f132ab98
export PHNET_ID=fd410e72-d29b-43bb-8b8a-8ac760469594
export NETOFF_ID=34465e19-632e-4e9f-8a46-c79d79c1e758
cmk updateZone id=$ZONE_ID allocationstate=Disabled
cmk create physicalnetwork zoneid=$ZONE_ID name="SVANet" isolationmethods=None tags=net27
cmk add traffictype physicalnetworkid=$PHNET_ID traffictype=Guest kvmnetworklabel=cloudbr1
cmk update physicalnetwork id=$PHNET_ID state=Enabled
cmk create networkoffering name="L2 No VLAN" guestiptype=L2 supportedservices="" traffictype=Guest specifyvlan=false ispersistent=true tags=net27
cmk update networkoffering id=$NETOFF_ID state=Enabled
cmk updateZone id=$ZONE_ID allocationstate=Enabled
cmk create network name="L2 Guest No VLAN" displaytext="L2 Guest SVA" zoneid=$ZONE_ID networkofferingid=$NETOFF_ID physicalnetworkid=$PHNET_ID
What to do about it?
This will be the simplest network configuration for a typical native KVM environment. In our case, "flat" clusters and backup networks not routed. How can the problem be solved?
problem
Error Unable to convert network offering with specified id to network profile with
Not possible to define the L2 guest network without VLAN.
versions
CloudStack 4.20.1.0
Ubuntu 24.04.2
Bridge configuration:
The steps to reproduce the bug
debug-error.txt
What to do about it?
This will be the simplest network configuration for a typical native KVM environment. In our case, "flat" clusters and backup networks not routed. How can the problem be solved?