Hudratronium opened a new issue, #6698:
URL: https://github.com/apache/cloudstack/issues/6698

   <!--
   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.
   -->
   ~~~
   API, UI, SSVM, CPVM
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main 
branch.
   -->
   
   ~~~
   4.17.0.1
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, 
advanced networking, etc.  N/A otherwise
   -->
   1 Zone, Advanced networking, 3 domains
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   All running Ubuntu 20.04.5
   Database mysql 8
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   Existing configuration (working running CS 4.16.1)
   <img width="250" alt="System_Root" 
src="https://user-images.githubusercontent.com/79725167/188282078-7a44bfa9-d468-4e44-ab0b-6e4c1afa0550.png";>
   
   <img width="378" alt="details" 
src="https://user-images.githubusercontent.com/79725167/188282087-fe71e735-ed7c-43b3-a76f-7cce7cb3bff5.png";>
   
   Setting `system.vm.public.reservation.mode.strictness` = true
   
   After upgrade:
   While deploying SSVM / CPVM, dedicated IP Ranges for use of system VMs 
aren't concidert for deployment. With 
`system.vm.public.reservation.mode.strictness` enabled, a deployment of SSVM / 
CPVM fails "due to Insufficent address capacity".
   With `system.vm.public.reservation.mode.strictness` set to 'false' 
deployment is successfull while using IP ranges not marked as dedicated for 
system VMs.
   Newly created IP ranges with dedication for systemVMs aren't stored or found 
in db table `domain_vlan_map`. Also prior used ip ranges dedicated for 
systemVMs aren't referenced in `domain_vlan_map`.
   
   Currently tested with public IP addresses. Not tested with "strictness" for 
management IP addresses.
   
   
   
   ##### 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.
   -->
   
   - Create IP range for public IPs with dedication for system VMs enabled
   - Change setting `system.vm.public.reservation.mode.strictness` to true
   - Destroy existing CPVM / SSVM
   
   
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   - Table `domain_vlan_map` shows entry for newly created IP range (stored as 
new vlan) assigned to domain
   - System VMs are successfully deployed using IPs from the dedicated IP range
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   - Table `domain_vlan_map` shows no entry
   - Deployment of systemVMs  fails due to insufficent address capacity
   - Changeing setting `system.vm.public.reservation.mode.strictness` to "false"
      --> deployment successfull using IP range of domain not dedicated for 
systemVMs
   ~~~
   


-- 
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]

Reply via email to