[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734331#comment-13734331
 ] 

Naoki Sakamoto commented on CLOUDSTACK-3533:
--------------------------------------------

I think you ask me about following result (no_dhcp_release) in "edithosts.sh".

=======================================
(L83)
command -v dhcp_release > /dev/null 2>&1
no_dhcp_release=$?

(L104)
if [ $no_dhcp_release -eq 0 ]
then
  #release previous dhcp lease if present
  logger -t cloud "edithosts: releasing $ipv4"
  dhcp_release eth0 $ipv4 $(grep "$ipv4 " $DHCP_LEASES | awk '{print $2}') > 
/dev/null 2>&1
  logger -t cloud "edithosts: released $ipv4"
fi
=======================================


Virtual Router
/var/log/messages

(on issue time)
Aug  8 08:53:01 r-11-VM cloud: Password server failed with error code 1. 
Restarting socat...
Aug  8 08:53:04 r-11-VM cloud: Password server failed with error code 1. 
Restarting socat...
Aug  8 08:53:07 r-11-VM cloud: Password server failed with error code 1. 
Restarting socat...
Aug  8 08:53:10 r-11-VM cloud: Password server failed with error code 1. 
Restarting socat...
Aug  8 08:53:13 r-11-VM cloud: Password server failed with error code 1. 
Restarting socat...
Aug  8 08:53:16 r-11-VM cloud: edithosts: releasing 10.0.0.2
Aug  8 08:53:16 r-11-VM cloud: edithosts: released 10.0.0.2
Aug  8 08:53:16 r-11-VM cloud: edithosts: update 02:00:5d:19:00:09 10.0.0.2  
sakamoto035 to hosts
Aug  8 08:53:16 r-11-VM cloud: Password server failed with error code 1. 
Restarting socat...
Aug  8 08:53:19 r-11-VM cloud: Password server failed with error code 1. 
Restarting socat...
Aug  8 08:53:22 r-11-VM cloud: Password server failed with error code 1. 
Restarting socat...
Aug  8 08:53:25 r-11-VM cloud: Password server failed with error code 1. 
Restarting socat...
Aug  8 08:53:28 r-11-VM cloud: Password server failed with error code 1. 
Restarting socat...


I found "edithosts: releasing 10.0.0.2" and "edithosts: released 10.0.0.2".
Then I think no_dhcp_release = 0 at that time.


If you ask me the command existence.
I execute "which" like following.

root@r-11-VM:~# which dhcp_release
/usr/bin/dhcp_release
root@r-11-VM:~#

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

Reply via email to