You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sheng Yang (JIRA)" <ji...@apache.org> on 2013/07/19 00:46:50 UTC

[jira] [Reopened] (CLOUDSTACK-3533) [IPv6][dnsmasq] VM not able get ip from dhcp which is previously assigned to vm

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sheng Yang reopened CLOUDSTACK-3533:
------------------------------------


According to: http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2013q2/007077.html

Simon(the author of dnsmasq) claimed that dhcp_release didn’t support IPv6 lately. Simon also said there are some bugs in the early dnsmasq releases.

I need to check with Simon about if we can use dhcp_release on ipv6 address.
                
> [IPv6][dnsmasq] VM not able get ip from dhcp which is previously assigned to vm
> -------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3533
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3533
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Devices
>    Affects Versions: 4.2.0
>            Reporter: Jayapal Reddy
>            Assignee: Sheng Yang
>             Fix For: 4.2.0
>
>
> 1. Create a guest network with small ip range (ex: max ips 3)
> 2. Deploy VMs utill ip address exhaust.
> 3. Now delete the one vm ex: V3 . Here one IP got freed.
> 4. deploy new vm Ex: name V4. Now the V4 supposed to get ip address which is release by V3.
> Issue 1:
> V4 is not getting ip address.
> Issue 2:
> 1.destroy vm ex: v1 with ipv1.
> 2. create a vm ex:v2. v2 got ip address of v1.
> 3. Now observe the dhcphosts.txt. It contains the two entries for with same IP.
> edithosts.sh failed to delete entry with ip already in dhcphosts.txt 

--
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