You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Advanced zone with 4 physical networks
Public
Management
Guest (1) - VXLAN isolation, tag: vxlan
Guest (2) - VLAN Isolation, tag: vlan
OS / ENVIRONMENT
ACS 4.19.1.1 , KVM
SUMMARY
After creating a zone with the above configuration I could create an isolated guest network on Guest (1), and a shared guest network on Guest (2). But the network offering other than the 'quick cloud no service' no other network offering is listed. This issue remains even after removing the second physical network with the guest traffic.
The listing works fine after removing the tag on the physical networks. Tagging existing physical network with guest is mandatory to add another physical network and add a traffic type guest to it.
STEPS TO REPRODUCE
1. Create an advanced zone with 4 physical networks having traffic types Public, Management, Guest , Guest.
2. One of the Guest can be VXLAN, other can be VLAN although not sure if it is causing the issue.
3. Tag the physical networks having guest traffic.
4. Create a network offering with a tag matching one of the physical network having guest traffic.
5. Create a guest network.
EXPECTED RESULTS
Network offerings get listed.
ACTUAL RESULTS
Network offerings do not get listed.
The text was updated successfully, but these errors were encountered:
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
Advanced zone with 4 physical networks
Public
Management
Guest (1) - VXLAN isolation, tag: vxlan
Guest (2) - VLAN Isolation, tag: vlan
OS / ENVIRONMENT
ACS 4.19.1.1 , KVM
SUMMARY
After creating a zone with the above configuration I could create an isolated guest network on Guest (1), and a shared guest network on Guest (2). But the network offering other than the 'quick cloud no service' no other network offering is listed. This issue remains even after removing the second physical network with the guest traffic.
The listing works fine after removing the tag on the physical networks. Tagging existing physical network with guest is mandatory to add another physical network and add a traffic type guest to it.
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: