[
https://issues.apache.org/jira/browse/CLOUDSTACK-10252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16337163#comment-16337163
]
ASF GitHub Bot commented on CLOUDSTACK-10252:
---------------------------------------------
rhtyd commented on issue #2427: CLOUDSTACK-10252: Delete dnsmasq leases file on
restart
URL: https://github.com/apache/cloudstack/pull/2427#issuecomment-360063571
@DaanHoogland that's right, the aim of the PR was scoped only to fix the
blocker. Perhaps for 4.11.1+ we can aim to improve changing the leases file
instead of removing it, how it used to be done before it was removed:
https://github.com/apache/cloudstack/commit/73c0242df355a29ffdddd3134f6288a63dd3f1df#diff-3ab4e2009108bf42111df9efc71f0f03R98
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> VR Problem on Releasing Expunged Instance IP from dnsmasq.leases file
> ---------------------------------------------------------------------
>
> Key: CLOUDSTACK-10252
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10252
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Priority: Blocker
> Fix For: 4.11.0.0
>
>
> Email on dev@:
> Hi;
> Today we noticed that one of our new provisioned instance did not get IP
> from VR. When we dig into the issue we find that one different mac is
> written in dnsmasq.leases file holds new instances IP address.
> We checked this mac address from db and we noticed that this mac is used
> for old expunged instance.
> So from this point we realised that when we destroy an instance its mac did
> not removed from dnsmasq.leases file so if we use this ip for a new
> instance then we have a problem, our instance could not get IP from VR.
> We have one host on our lab environment and its Ubuntu 16.04.3 KVM. Today
> we made a HA test and we crashed the host so VR and SystemVM's are rebooted
> after we boot host back. I do not think this issue is related to VR reboot
> but i like to give information about our environment.
> We need to manage dnsmasq.leases file when we expunge an instance.
> Thanks
> Özhan
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
