[jira] [Created] (CLOUDSTACK-3424) IPV6 - When a Vm is expunged and a new Vm is deployed with the same name , /etc/dhchosts.txt has 2 entries with the same name.

["Sangeetha Hariharan (JIRA)" <ji...@apache.org>]

Sangeetha Hariharan created CLOUDSTACK-3424:
-----------------------------------------------

             Summary: IPV6 - When a Vm is expunged and a new Vm is deployed with the same name , /etc/dhchosts.txt has 2 entries with the same name.
                 Key: CLOUDSTACK-3424
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3424
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
    Affects Versions: 4.2.0
         Environment: Build from master-6-17-stable
            Reporter: Sangeetha Hariharan
             Fix For: 4.2.0


IPV6 - When a Vm is expunged and a new Vm is deployed with the same name , /etc/dhchosts.txt has 2 entries with the same name

Steps to reproduce the problem:

Create a ipv6 network.
Deploy a Vm with name - test456.
Destroy this VM. Wait for it to be expunged.
Deploy another Vm with same name - test456.

We see that there are 2 entries in the router with the same name "test456" resolving to 2 different ipv6 addresses.

root@r-17-VM:~# cat /etc/dhcphosts.txt
id:00:03:00:01:06:4e:de:00:00:2f,[fc00:3:1370::744f],test123,infinite
id:00:03:00:01:06:75:46:00:00:31,[fc00:3:1370::34ed],test456,infinite
id:00:03:00:01:06:e4:ae:00:00:32,[fc00:3:1370::ae4b],testyoyo,infinite
id:00:03:00:01:06:96:aa:00:00:33,[fc00:3:1370::34ed],testyoyo1,infinite
id:00:03:00:01:06:cb:88:00:00:34,[fc00:3:1370::6eb2],test456,infinite
root@r-17-VM:~#

Attaching management server logs:

Have 2 entries for the same name is a problem.

Is it also a problem to have the same ipv6 address associated with 2 different vms with different Vm names ( 1 expunged and 1 active , in my case "test456" which is expunged and "testyoyo1" which is active) ?



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira