Skip to content

Network->Security groups not shown after wizard #9853

Description

@rp-
ISSUE TYPE
  • Bug Report
COMPONENT NAME
UI
CLOUDSTACK VERSION
4.19.1.2
CONFIGURATION

basic network, with security group offering

OS / ENVIRONMENT

almalinux9, kvm

SUMMARY

After a fresh install and doing the setup wizard, the Network->Security groups UI item will not be shown until you restart
the cloudstack-management service and relog.

STEPS TO REPRODUCE
Do a fresh CloudStack install
Run through the wizard with basic zone + security groups
EXPECTED RESULTS
Security group entry without restarting the cloudstack-management service.
ACTUAL RESULTS
Security groups item is missing, and maybe other too?(Guest VLAN)

Activity

  1. DaanHoogland commented on Oct 28, 2024

    @DaanHoogland
    Contributor

    @rp- , is this really a bug? it seems not unreasonable to expect a reboot after such a fundamental change to the (default) system configuration.
    Maybe it is more appropriate to have a message indicating an MS restart is needed?

  2. weizhouapache commented on Oct 28, 2024

    @weizhouapache
    Member

    @rp- , is this really a bug? it seems not unreasonable to expect a reboot after such a fundamental change to the (default) system configuration. Maybe it is more appropriate to have a message indicating an MS restart is needed?

    a logout-login should work.

  3. rp- commented on Oct 28, 2024

    @rp-
    ContributorAuthor

    @rp- , is this really a bug? it seems not unreasonable to expect a reboot after such a fundamental change to the (default) system configuration. Maybe it is more appropriate to have a message indicating an MS restart is needed?

    a logout-login should work.

    I thought I did that...

    But would a auto-logout not be good then?

  4. DaanHoogland commented on Oct 28, 2024

    @DaanHoogland
    Contributor

    @rp- , is this really a bug? it seems not unreasonable to expect a reboot after such a fundamental change to the (default) system configuration. Maybe it is more appropriate to have a message indicating an MS restart is needed?

    a logout-login should work.

    I thought I did that...

    But would a auto-logout not good then?

    sounds reasonable. with message?

  5. weizhouapache commented on Oct 28, 2024

    @weizhouapache
    Member

    @rp- , is this really a bug? it seems not unreasonable to expect a reboot after such a fundamental change to the (default) system configuration. Maybe it is more appropriate to have a message indicating an MS restart is needed?

    a logout-login should work.

    I thought I did that...

    But would a auto-logout not be good then?

    the reason is, the zones information is cached in browser (store.getters.zones). It is not automatically updated when create a new zone (yes, it should be updated).
    when logout and then login, zones info will be reloaded I think.

  6. added this to the 4.21.0.0 milestone on Nov 8, 2024
  7. added theissue type on Jul 11, 2025
  8. removed this from the 4.21.0 milestone on Aug 29, 2025
  9. 3 remaining items

  10. modified the milestones: 4.22.1, 4.22.2 on Apr 24, 2026
  11. github-actions commented on Aug 25, 2026

    @github-actions

    This issue is stale because it has been open for 120 days with no activity. It may be removed by administrators of this project at any time. Remove the stale label or comment to request for removal of it to prevent this.

  12. modified the milestones: 4.22.2, 4.20.4 on Aug 25, 2026
  13. linked a pull request that will close this issuerefresh zones in the client view #13974on Aug 25, 2026
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

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions