[GitHub] [cloudstack] andrijapanicsb edited a comment on issue #3272: VR DHCP lease file not persistent

[GitBox <gi...@apache.org>]

andrijapanicsb edited a comment on issue #3272: VR DHCP lease file not persistent
URL: https://github.com/apache/cloudstack/issues/3272#issuecomment-546035699
 
 
   Not really... (partially solved i.e. we don't wipe any more the dnsmasq.leases file - we just remove the specific IP/MAC settings from the CONFIGURATION files for dnsmasq, BUT at the wrong point in time - causing other issues). This is solved now in master - i.e. we delete specific IP/MAC CONFIGURATION only when expunging the VM (i.e. not while starting) 
   
   Outstanding issues: restarting Network with CleanUP - inside the new VR that is created during network restart, dnsmasq.leases file is absent  - this will cause clients to receive DHCPNAK when they try to renew the lease with DHCPREQUEST. Client's will then failback to the "initialisation process" with DHCPDISCOVER and get's it's IP address - no downtime from IP connectivity point of view - i.e. the client will NOT lose it's IP address at any point in time.
   
   BUT, on some RHEL system, this DHCPNAK will cause RHEL system to drop its routes... thus the problem. This is an edge case.
   
   We yet need to solve that the new VR (that is created during network restarts with CleanUp) to also get the dnsmasq.leases file regenerated somehow (if possible)....
   Current 4.11.3 and 4.13 are causing issues as following:
   - VMware DRS - sometimes on busy clusters, the powerON report (from vSphere to ACS) will come a bit too late after the previous PowerOFF report (those are generated while LIVE migrating VMs via vSphere as opposed to via ACS) - and then ACS will say "ok, VM is off - let me remove it's IP/MAC addresses from the related CONFIGURATION files for dnsmasq) - and this will again lead to VM being unable to renew its IP address eventually.
   
   Hope that clarifies the current situation with 4.11.3/4.13 - it's good to be documented somewhere, thus my looooooong comment here.
   
   
   
   
   
   
   
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services