[
https://issues.apache.org/jira/browse/CLOUDSTACK-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13651498#comment-13651498
]
Sangeetha Hariharan commented on CLOUDSTACK-2370:
-------------------------------------------------
The Vm that was expunged was "test-5" with ip address - 10.223.161.113.
The Vm that was deployed with the same ip address - 10.223.161.113 is "test-new.
Management and smlogs attached.
> PVLAN - Vm that is deployed with Ip address that was previously associated
> with an expunged Vm is not assigned a Ip address.
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2370
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2370
> 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 pvlan branch
> Reporter: Sangeetha Hariharan
> Fix For: 4.2.0
>
> Attachments: logs.rar
>
>
> Set up : Advance zone Create
> 1. Create a Shared NW1 by passing private vlan Id along with the regular
> Vlan Id.
> 2. Deploy few Vms in this network.
> 3. Destroy VM.
> 4. Wait for the Expunge interval to pass.
> 5. Deploy a Vm using the same Ip address as the expunged Vm.
> 6. Vm deployment shoud succeed.
> 7. As part of this VM deployment, router's /etc/dhcphost entry for the
> expunged Vm gets deleted and the entry pertaining to the new Vm is created.
> But VM fails to get an Ipaddress.
> Once the dnsmasq process is restarted , Vm is able to get an Ip address.
--
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
