Hudratronium commented on issue #6698:
URL: https://github.com/apache/cloudstack/issues/6698#issuecomment-1238124169

   @shwstppr 
   Just to be shure:
   And with `system.vm.public.reservation.mode.strictness` = "true" **and** 
`use.system.public.ips` = "false" the deployment worked for you?
   Have you more then the Root Domain deployed in your zone?
   
   As i said i am just curious as this configuration has been working until i 
upgraded twards 4.17.0.1. Might be that something went wrong during the upgrade 
of the Management-Server.
   However from the logs of the SQL - statements everything is working as one 
would expected from a logical point.
   
   > When For system VMs is selected in the UI it correctly marks the IPs from 
the range for system VMs even when domain is selected (also with API, 
https://github.com/apache/cloudstack/issues/6698#issuecomment-1236621729).
   
   It does indeed - but that doesn't help when during the allocationprocess the 
group of vlans gathered for a domain isn't containing the vlan-id, which is 
used to reference to the IP range  (IP - addresses) dedicated to systemVMs.
   From the GUI point of view literally nothing has changed after the upgrade 
and everything is shown correctly.
   
   Maybe you could share a log of the deploying sequence with "trace"-logging 
so that i can look up to it if they differ ?
   
   > Traditionally, I don't see any linkage between domain and system VMs.
   At least from the overall architecture in my understanding this is going to 
be relevant if one is working with mulitple zones as well as "Dedicated Zones" 
for different Domains / Accounts - depending of course on what one wants to 
achieve.
   
   @nvazquez just mentioning you here as you asked me to raise the issue and i 
don't know if i informed you about this on the mailinglist
   
   


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