GitHub user nickaccuweb added a comment to the discussion: Cloudstack 4.22 - Configuration Wizard failing - Fix Error
@soulfulgent Thanks for testing that and sharing the screenshots. This is actually a useful result. You've now successfully created a Shared Guest Network using untagged on Physical Network 2, without specifying a Virtual Router IP. This tells us that CloudStack is capable of accepting an untagged Guest network in your existing Advanced Zone configuration. So your original plan of using two NICs, with Management/Storage on one and Guest traffic on the other, looks achievable without introducing VLAN 800 just to satisfy the wizard. **Why does it work manually but not through the wizard?** I suspect there may be a difference in how the configuration wizard handles the VLAN field compared with the standalone network creation form. When you left the VLAN field blank in the wizard, it failed. However, the standalone form accepted the explicit value untagged and created the network successfully. That suggests the wizard may not be passing or interpreting the VLAN parameter correctly, although we'd need to compare the API requests to confirm that. There is also something worth noting: your new network is currently showing the **Setup** state, rather than being fully operational. This is expected at this stage because you haven't added your KVM hosts or storage yet. **Where do we go from here?** I suggest we stop using the configuration wizard for now and complete the existing Zone manually, rather than rebuilding the database again. Before doing that, I'd recommend the following: 1. **Verify the Guest network:** Confirm that SHARED_NETWORK is associated with Physical Network 2 (cloudbr1) and uses the security-group-enabled shared network offering. 2. **Verify the SecurityGroupProvider:** Under Physical Network 2 → Network service providers, confirm that SecurityGroupProvider is enabled. 3. **Review the existing Guest networks:** You now have two Guest networks: the original defaultGuestNetwork using VLAN 800 and the new SHARED_NETWORK using untagged. Since your goal is to avoid VLAN tagging, we should decide which network to retain before proceeding. 4. **Check the Guest subnet:** Your screenshots show 30.30.30.0/24, although you mentioned 20.20.20.0/24 in your message. Both are outside the RFC 1918 private address ranges. For a private Guest network, I'd recommend using an unused RFC 1918 subnet instead. 5. **Continue the infrastructure setup:** Once the network configuration is finalized, proceed with adding the cluster, KVM host, primary storage and secondary storage through the CloudStack UI. 6. **Enable the Zone:** After the required resources have been added and verified, enable the Zone and test deploying a VM on the untagged shared Guest network. One important point: successfully creating the network doesn't yet confirm that DHCP, connectivity or security-group filtering works. We'll be able to verify those after adding a host and deploying a test VM. **Do we need to change CloudStack versions?** Not at this point. Since manual network creation is working, I would continue with your existing 4.22 installation and investigate the wizard separately. If we can reproduce the difference between the manual and wizard API requests, it would be worth raising it as a possible CloudStack UI issue. For reference, the official documentation covers this configuration: https://docs.cloudstack.apache.org/en/4.22.0.0/adminguide/networking/advanced_zone_config.html https://docs.cloudstack.apache.org/en/4.22.0.0/adminguide/networking/security_groups.html I think we're now in a better position than before. We've confirmed that creating an untagged Guest network works, so rather than repeatedly restarting the setup process, I'd focus on completing the existing Zone and testing the network with an actual VM. Regards, Nick R AccuWeb.Cloud GitHub link: https://github.com/apache/cloudstack/discussions/13956#discussioncomment-19762071 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
