GitHub user nickaccuweb added a comment to the discussion: Cloudstack 4.22 - Configuration Wizard failing - Fix Error
@soulfulgent Thanks for clarifying your network setup. That helps. Yes, your intended configuration is possible with CloudStack Advanced Networking and Security Groups, particularly with KVM and Linux bridges. You can use your two NICs as follows: - NIC 1 (cloudbr0): Management and Storage traffic, untagged. - NIC 2 (cloudbr1): Guest traffic, untagged, using a shared network with Security Groups. You don't necessarily need VLAN tagging for this setup, provided the physical networks are correctly separated. Also, since you've only created the Zone, POD, and networks so far, having no hosts or storage configured is fine at this stage. I wouldn't consider that the cause of the wizard failure. Regarding Physical Network 2 showing VLAN as its isolation method, this doesn't automatically mean every network must use a numbered VLAN. CloudStack supports untagged shared networks as well. Here's what I suggest next: 1. Keep the existing Zone and POD for now. No need to reset the database again. 2. Since defaultGuestNetwork was created using VLAN 800, don't assume it is suitable for your intended untagged network. 3. Check whether CloudStack allows you to create a new Shared Guest Network outside the wizard, selecting Physical Network 2, the security-group-enabled network offering, and untagged for VLAN/VNI. 4. Make sure the SecurityGroupProvider is enabled on Physical Network 2. VirtualRouter being enabled doesn't necessarily confirm that SecurityGroupProvider is enabled. 5. If the UI rejects the untagged network, please share the exact error and corresponding API response. That would help us determine whether we're dealing with a CloudStack 4.22 wizard limitation or a network-offering configuration issue. Since your Guest network uses a dedicated NIC, there should be no need to assign VLAN 800 simply to separate it from Management and Storage. I would also avoid enabling the Zone or adding hosts until we've confirmed the intended Guest network configuration. Regarding trying another version: I wouldn't switch versions yet. First confirm your exact 4.22 patch release and test the untagged shared-network creation separately. If the API supports the configuration but the wizard rejects it, we may have a reproducible wizard issue worth reporting. Reference: https://docs.cloudstack.apache.org/en/latest/adminguide/networking/security_groups.html Let us know what happens when you try creating the untagged shared Guest network outside the wizard. Regards, Nick R AccuWeb.Cloud GitHub link: https://github.com/apache/cloudstack/discussions/13956#discussioncomment-19429453 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
