Skip to content

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

Closed

Description

@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
cloudstack_network


Activity

  1. boring-cyborg commented on Jun 10, 2024

    @boring-cyborg

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

  2. rajujith commented on Jun 11, 2024

    @rajujith
    Contributor

    @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?

  3. DensonNgumo commented on Jun 11, 2024

    @DensonNgumo
    Author

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

  4. weizhouapache commented on Jun 11, 2024

    @weizhouapache
    Member

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

    @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>
    
  5. added this to the 4.19.1.0 milestone on Jun 11, 2024
  6. DensonNgumo commented on Jun 13, 2024

    @DensonNgumo
    Author

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

  7. DaanHoogland commented on Jun 13, 2024

    @DaanHoogland
    Contributor

    @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?

  8. weizhouapache commented on Jun 13, 2024

    @weizhouapache
    Member

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

    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 ?

  9. DensonNgumo commented on Jun 13, 2024

    @DensonNgumo
    Author

    @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.

  10. DensonNgumo commented on Jun 13, 2024

    @DensonNgumo
    Author

    @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.

  11. weizhouapache commented on Jun 13, 2024

    @weizhouapache
    Member

    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" ?

  12. 20 remaining items

  13. yadvr commented on Jul 29, 2024

    @yadvr
    Member

    To add to what @borisstoyanov has shared, this usually can happen if the zone deployment form has errors or for some reason the zone deployment didn't go as expected (for example silent errors) and only then offerings are not listed as the zone doesn't have the right supported network service providers enabled/configured.

    @GeorgeLisandru can you go to the UI -> Infrastructure -> Zone -> select your zone -> go the physical network and select that -> click on the network service providers (NSP) tab; and share screenshot of this page. Do you see the VirtualRouter and VPCVirtualRouter network service providers in red (i.e. disabled)? If they are indeed disabled, can you try to enable them and see if you can then see the network offerings listed?

  14. GeorgeLisandru commented on Jul 29, 2024

    @GeorgeLisandru

    Thank you very much for your answers!

    Indeed this is the case. I have VirtualRouter, VPCVirtualRouter and InternalLbVm in stop state and I am not able to start any of them. Below is a screenshot of the error message that I get.

    image

  15. DensonNgumo commented on Jul 29, 2024

    @DensonNgumo
    Author

    @DensonNgumo @UAnton can you try to upgrade to 4.19.1.0 and also suggest following checklist:

    • Do you have the zone enabled and specific network service providers also enabled
    • Can you share screenshot from your zone's physical networks' network service providers tab
    • Can you try this in a private browser tab/window?
    • Do you have available/free VLANs in that zone

    Hi,
    Yes, the zone was enabled. On initial setup everything worked as expected and I never got any errors during installation, had even created my first shared network. The network service providers are enabled as shown below:
    cs-physical_network
    Once I observed the issue is when I upgraded from 4.18 to 4.19 but the issue remained.

  16. borisstoyanov commented on Jul 30, 2024

    @borisstoyanov
    Contributor

    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.
  17. DensonNgumo commented on Jul 30, 2024

    @DensonNgumo
    Author

    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.

  18. DensonNgumo commented on Sep 6, 2024

    @DensonNgumo
    Author

    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.
    cmk-network

  19. DensonNgumo commented on Sep 6, 2024

    @DensonNgumo
    Author

    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. cmk-network

    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.

  20. int0x21 commented on Sep 18, 2024

    @int0x21

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

  21. DensonNgumo commented on Sep 20, 2024

    @DensonNgumo
    Author

    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.

  22. locked and limited conversation to collaborators on Sep 20, 2024
  23. converted this issue into a discussion #9716 on Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions