zap51 opened a new issue, #7790:
URL: https://github.com/apache/cloudstack/issues/7790
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
UI, API
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
Tested v4.16.1.0 onwards
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
~~~
Advanced networking
~~~
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
~~~
Ubuntu 20.04 and later
~~~
##### SUMMARY
<!-- Explain the problem/feature briefly -->
On adding a new zone from the WebUI and when the Physical Network for Guest
traffic is specifically chosen as VXLAN, zone creation fails as the VNIs can
not be set greater than 4095
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
1. Use the wizard on WebUI to create a new zone.
2. Choose Advanced Networking.
3. Add details of the zone and choose KVM.
4. Create physical networks as follows
5. Add Public and System VM networks.
6. Add the VNI ranges greater than 4095
7. During the final addition, an exception is thrown saying VLAN or VNI
ranges should be in range 0 - 4095.
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
The zone addition with VXLAN isolation should go through when the VNI ranges
are greater than 4095 for Guest Network.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
During the final addition, an exception is thrown saying VLAN or VNI ranges
should be in range 0 - 4095. Also, let's say we input 3701 - 3702 as the dummy
ranges during addition, the range "3701 - 3702" actually gets applied on
"Public Network" as dynamic range of VLANs. The Physical Network for "Guest"
still doesn't have any dynamic VLAN IDs or VNIs hence manual addition is
required.
~~~
Thanks,
Jayanth Reddy
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
