Hudratronium commented on issue #6698: URL: https://github.com/apache/cloudstack/issues/6698#issuecomment-1236740037
@shwstppr at least it occurs to me that in my current setup the missing entry in the `cloud.domain_vlan_map` seems to be the crucial thing missing. I can create a new dedicated range for the domain but it isn't represented in the `cloud.domain_vlan_map` table. Which seems to be crucial in the overall "search" for a fitting IP-Range. I don't know why this isn't updated / the existing configuration doesn't work out anymore. Maybe some more infos regarding our global conf: `use.system.public.ips` = false `system.vm.public.reservation.mode.strictness` = true From my reading of the trace-log above the process ist: 1. Check if the account has dedicated vlans --> result is "none" 2. Check if the domain has dedicated vlans --> results are all vlan for a domain, but missing the one for use with systemVMs as it isn't present in `cloud.domain_vlan_map` 3. Check if there are any vlans NOT assigned to a account or domain --> result it the correct VLAN (guess that would be the check if there is a "systempool") --> not choosen as `use.system.public.ips` = false 4. Looking up setting `strictness ` --> if true only domain related VLANs shall be checked / `user_ip_address.forsystemvms` setting is irrelevant 5. lookup IPs - depenending on assigned vlans of the domain - and check for IPs which are not assigned and `user_ip_address.forsystemvms = 1` --> fails as the "correct" vlan isn't in the results of the former querys as it is missing in db table -- 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]
