Creating Guest Network: unable to choose Network Offering. This for all L2,Shared and Isolated networks

[DensonNgumo]

ISSUE TYPE

• Bug Report

COMPONENT NAME

UI

CLOUDSTACK VERSION

4.18.0

4.19.0.1

CONFIGURATION

Advanced networking configured

OS / ENVIRONMENT

Management servers running on Ubuntu 22.0.4

SUMMARY

I want to create new guest networks. On the network creation window I am unable to choose any network offering. The default system network offerings as well my custom network offerings exist but on the dropdown none appear. I am thus unable to create a L2 network which will allow me to specify the VLAN.

STEPS TO REPRODUCE

1. Navigate to Add Network.
2.  Pick either 'Shared', 'L2' or 'Isolated'
3.  Try to specify a network offering under the dropdown provided.

EXPECTED RESULTS

All the available network offerings should be available for selection under the drop down.

ACTUAL RESULTS

No network offering is available for selection

[boring-cyborg[bot]]

Thanks for opening your first issue here! Be sure to follow the issue template!

[rajujith]

@DensonNgumo I see 4 network offerings for this drop-down in ACS 4.19.0.0. Can you check whether any L2 network offering is enabled?

[DensonNgumo]

Despite the default offerings, I have also created my own to test and it still does not appear.

[weizhouapache]

Despite the default offerings, I have also created my own to test and it still does not appear.

@DensonNgumo
it works fine in my environment with 2 hypervisor types.

can you use cmk to list the network offering ?

cmk list networkofferings guestiptype=L2 filter=id,name zoneid=<uuid of zone>

[DensonNgumo]

If I specify the zone id then I am not seeing the offerings but if I don't, then I can.

[DaanHoogland]

@DensonNgumo I see all offerings in both cases. and lso with or without the guestiptype=L2.

Did you create any offerings yourself?
Did you create this zone (and enable it) before or after creating any offerings?

You say you see this in 4.18.0 and in 4.19.0.

Did you upgrade and tested again, or create a new installation?

Can you create a new offering, with the same parameters and see if this displays?

[weizhouapache]

If I specify the zone id then I am not seeing the offerings but if I don't, then I can.

I suspect it is caused by the network offering "SIP_Network" created by you @DensonNgumo
can you upload network_offerings table and network_offering_details table ?

[DensonNgumo]

@DensonNgumo I see all offerings in both cases. and lso with or without the guestiptype=L2.

Did you create any offerings yourself? Did you create this zone (and enable it) before or after creating any offerings?

You say you see this in 4.18.0 and in 4.19.0.

Did you upgrade and tested again, or create a new installation?

Can you create a new offering, with the same parameters and see if this displays?

I created the one labeled 'SIP_Network' to test if the issue was the default offerings. The issue was there without the custom offering.

[DensonNgumo]

@DensonNgumo I see all offerings in both cases. and lso with or without the guestiptype=L2.

Did you create any offerings yourself? Did you create this zone (and enable it) before or after creating any offerings?

You say you see this in 4.18.0 and in 4.19.0.

Did you upgrade and tested again, or create a new installation?

Can you create a new offering, with the same parameters and see if this displays?

The issue was first observed in version 4.18.0. I then upgraded to 4.19.0 to see if it would resolve but there was no change. The Zone had been created during the initial setup. The zone was up and enabled before any custom offerings. The custom offering was created just to troubleshoot the issue.

[weizhouapache]

SIP_Network

@DensonNgumo can you remove this offering if it is not in use ?
can you update the access of offering "DefaultL2NetworkOfferingConfigDriveVlan" to "Public" to "All zones" ?

[DaanHoogland]

yes, so in case you don't know; go through all the offerings that should be visible, press this button: , and update the access settings in the dialogs.

[DensonNgumo]

I have removed the custom offering. All the default offerings are set to "Public" access. Changing the zone to "All zones" leaves the field as blank.


Still not able to select a network offering.

[DaanHoogland]

ok, this is not as intended but what if you set the zone specifically for one of the offerings, do you then see it?

[DensonNgumo]

#9193 (comment)
That's how it was. The offering I wanted to use had the zone specified.
None of the offerings has a zoneid when pulling the info using cmk

[weizhouapache]

#9193 (comment)
That's how it was. The offering I wanted to use had the zone specified.
None of the offerings has a zoneid when pulling the info using cmk

That is strange.
I was not able to reproduce the issue. Everything looks good in my testing.
I believe @DaanHoogland is not able to reproduce either

Can you share the mgmt server log when list network offerings with zoneid?

[borisstoyanov]

I think we're looking at 2 separate issues.

@DensonNgumo could you please confirm the following:

1. current version to the dot
2. you can still reproduce the issue
3. please do an api call with cmk, trying to create a network with the offering you're not able to see, and send the management logs

@GeorgeLisandru in your case I believe you might need to:

1. execute the following with cmk: configure virtualrouterelement enabled=true id= [id of the VP provider]
2. if not successful please provide the logs.

[DensonNgumo]

I think we're looking at 2 separate issues.

@DensonNgumo could you please confirm the following:

1. current version to the dot
2. you can still reproduce the issue
3. please do an api call with cmk, trying to create a network with the offering you're not able to see, and send the management logs

@GeorgeLisandru in your case I believe you might need to:

1. execute the following with cmk: configure virtualrouterelement enabled=true id= [id of the VP provider]
2. if not successful please provide the logs.

My current version is 4.19.0.1. Issue is still present. I will attempt the same with cmk and share the logs.

[DensonNgumo]

I think we're looking at 2 separate issues.

@DensonNgumo could you please confirm the following:

1. current version to the dot
2. you can still reproduce the issue
3. please do an api call with cmk, trying to create a network with the offering you're not able to see, and send the management logs

@GeorgeLisandru in your case I believe you might need to:

1. execute the following with cmk: configure virtualrouterelement enabled=true id= [id of the VP provider]
2. if not successful please provide the logs.

Creating the network using api calls via cmk is successful.

[DensonNgumo]

I think we're looking at 2 separate issues.
@DensonNgumo could you please confirm the following:

1. current version to the dot
2. you can still reproduce the issue
3. please do an api call with cmk, trying to create a network with the offering you're not able to see, and send the management logs

@GeorgeLisandru in your case I believe you might need to:

1. execute the following with cmk: configure virtualrouterelement enabled=true id= [id of the VP provider]
2. if not successful please provide the logs.

Creating the network using api calls via cmk is successful.

I upgraded to the latest version 4.19.1.1 and the issue of not being able to select the network offering via the UI remains.

[int0x21]

This happens when you have a tag on the network, remove the tag and it works. Spent all day on this
Fresh install.

[sidescale]

During the automated zone creation process it strongly suggested you to "Tag" your interfaces, but you need to keep the Physical Interface untagged where your isolated networks with VLAN tags lives. If you make the mistake of tagging this interface it breaks everything down stream. The API for listing network offerings stops working completely when a zoneid is included (cs listNetworkOfferings zoneid=xyz) will return an empty list. Thus breaking the UI for the shared and layer2 networks in the process. I tagged my interface with the same name as the kvmnetworklabel.

[weizhouapache]

@sidescale
which ACS version do you use ?

[DensonNgumo]

This happens when you have a tag on the network, remove the tag and it works. Spent all day on this Fresh install.

Hi, please elaborate. Tag on which section exactly? I have not set any network tags on the offerings.

[samapraku]

@DensonNgumo tag on the physical network. I also had the same issue and removing the tag as mentioned by @int0x21 fixed it for me.

I think it is possibly related to this issue #6747 I opened back in 2022 regarding the same problem. The issue was closed but apparently the problem is still there

[int0x21]

When creating the zone and setting up network you get the option off setting tags on the physical network, that is what caused all the issues for me. I really like the potential of cloudstack but some of these things needs to be cleaned up.
@DensonNgumo I'm glad my suggestion solved your issue :)

[DensonNgumo]

I do confirm that removing the tag on the physical network did indeed resolve the issue. Thanks @int0x21

[rajujith]

@int0x21 hopefully this will be fixed in 4.19.2: #9673

[UAnton]

Hi,
This happens without tags. I again get this problem on 4.20.

[Pearl1594]

When you say that there are no tags @UAnton , do you mean, on the Physical network or the network offering(s)?
Because, for no tags on Physical network - then atleast the default offerings should get listed
(Side note: If the network offerings are tagged, they need to have a tag that matches the physical network)

[UAnton]

1. When I add all Traffic types to the one Physical Network - no Network Offerings
2. When I try to add 2 Physical Networks and separate MGMT traffic from Public and Guest - SystemVMs doesn't start.
   Every time I get the problems with CS network model.

[UAnton]

I was trying different variants, but every type has 2 problems. 1 - No network offerings. 2 - SystemVMs don't starting.
I read documentation, forums, and GitHub issues but nothing helped. Watch a video from ShapeBlue about Cloudstack and XCP-NG. Repeat Step-by-Step from the video but every time get this problem!

[sidescale]

4.20.1 Latest Release.  The tagging of the physical interface breaks the output of the api.  Honestly, I ran into a whole bunch of bugs during the deep dive, that was just the worst one.  Youve clearly been heavily refactoring the storage, the ui, and authentication systems.

…

---- On Wed, 06 Aug 2025 19:30:29 -0700 ***@***.*** wrote ---- https://github.com/sidescale which ACS version do you use ? — Reply to this email directly, #9716 (reply in thread) , or https://github.com/notifications/unsubscribe-auth/AOBLRJ24CUNGUBQYQZLIJDL3MK24LAVCNFSM6AAAAACDIM33R2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMBSG43TSMY . You are receiving this because you were mentioned.

[weizhouapache]

@sidescale
do you have the list of the bugs ?

Regarding the tags of physical networks, IMHO it is not a bug, but we do need to clarify it in cloudstack document.

[sidescale]

Let me try to remember, it was a long 24 hours of no sleep 😂  1)  Saml payload even when Saml is disabled  2) Lots of session authentication issues 3) The API url needs to be set in the UI config.json when using a non standard IP aka over a vpn to the management UI on a private network 4) Disabling VLAN tagging on shared networks doesnt work, but using the word "untagged" on a tagged network does, otherwise it throws an error adding a vnet to brctl 5) I cant remember off the top of head but there is an error like "listAttrbutes" that gets called in the UI thats not part of api 6) I had to run an alter table on network_offerings table to add is_default but Im not sure thats a real bug or not, but it did generate a trace during initial install.  There were more, but honestly I didnt document and barely slept.  Ive got it running pretty cleanly now.

…

---- On Wed, 06 Aug 2025 19:56:00 -0700 ***@***.*** wrote ---- 4.20.1 Latest Release.  The tagging of the physical interface breaks the output of the api.  Honestly, I ran into a whole bunch of bugs during the deep dive, that was just the worst one.  Youve clearly been heavily refactoring the storage, the ui, and authentication systems.

---- On Wed, 06 Aug 2025 19:30:29 -0700 ***@***.*** wrote ---- https://github.com/sidescale which ACS version do you use ? — Reply to this email directly, #9716 (reply in thread) , or https://github.com/notifications/unsubscribe-auth/AOBLRJ24CUNGUBQYQZLIJDL3MK24LAVCNFSM6AAAAACDIM33R2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMBSG43TSMY . You are receiving this because you were mentioned.

[weizhouapache]

thanks @sidescale

@rajujith has already created a doc PR
apache/cloudstack-documentation#481