cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "venkata swamybabu budumuru (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3312) [Automation] Basic Zone with SG - ip address are not getting assigned to VM
Date Thu, 04 Jul 2013 00:13:19 GMT

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

venkata swamybabu budumuru commented on CLOUDSTACK-3312:
--------------------------------------------------------

Here are the details on how to quickly reproduce this issue:

1. Login to cloudstack that has at least 1 advanced zone setup with XenServer
2. create a ISOLATED network with CIDR 10.1.1.1/30

Note : with the above CIDR, we can only deploy one VM with ip addr 10.1.1.2/30
3. deploy a VM using the above ISOLATED Network which gets the IP 10.1.1.2

Observations:

(i) I can see the following entry in dhcphosts.txt

root@r-77-QA:~# cat /etc/dhcphosts.txt 
02:00:4b:c7:00:03,set:10_1_1_2,10.1.1.2,626065ff-1b81-4e07-b436-18bf264c7c62,infinite

4. Make sure that you have set the expunge.interval/delay global settings to smallest value
ex: 60
5. destroy the instance that was deployed in step 2

Observations: 

(ii) I can see that vm destroyed successfully but the entries still exist in /etc/dhcphosts.txt.
(iii) due to this new VM deployment that tries to use the same ip i.e. 10.1.1.2 will fail
to get the dhcp IP as dhcphosts.txt says it is still assigned with destroyed VM mac address.
(iii) Here is the snippet from dnsmasq.log

Jul  3 23:54:33 dnsmasq-dhcp[2867]: read /etc/dhcphosts.txt
Jul  3 23:55:12 dnsmasq-dhcp[2867]: not using configured address 10.1.1.2 because it is leased
to 02:00:50:d6:00:01
Jul  3 23:55:12 dnsmasq-dhcp[2867]: DHCPDISCOVER(eth0) 02:00:4b:c7:00:03 no address available
Jul  3 23:55:14 dnsmasq-dhcp[2867]: not using configured address 10.1.1.2 because it is leased
to 02:00:50:d6:00:01
Jul  3 23:55:14 dnsmasq-dhcp[2867]: DHCPDISCOVER(eth0) 02:00:4b:c7:00:03 no address available
Jul  3 23:55:17 dnsmasq-dhcp[2867]: not using configured address 10.1.1.2 because it is leased
to 02:00:50:d6:00:01
Jul  3 23:55:17 dnsmasq-dhcp[2867]: DHCPDISCOVER(eth0) 02:00:4b:c7:00:03 no address available
Jul  3 23:55:22 dnsmasq-dhcp[2867]: not using configured address 10.1.1.2 because it is leased
to 02:00:50:d6:00:01
Jul  3 23:55:22 dnsmasq-dhcp[2867]: DHCPDISCOVER(eth0) 02:00:4b:c7:00:03 no address available
Jul  3 23:55:31 dnsmasq-dhcp[2867]: not using configured address 10.1.1.2 because it is leased
to 02:00:50:d6:00:01
Jul  3 23:55:31 dnsmasq-dhcp[2867]: DHCPDISCOVER(eth0) 02:00:4b:c7:00:03 no address available
Jul  3 23:55:42 dnsmasq-dhcp[2867]: not using configured address 10.1.1.2 because it is leased
to 02:00:50:d6:00:01
Jul  3 23:55:42 dnsmasq-dhcp[2867]: DHCPDISCOVER(eth0) 02:00:4b:c7:00:03 no address available
Jul  3 23:55:59 dnsmasq-dhcp[2867]: not using configured address 10.1.1.2 because it is leased
to 02:00:50:d6:00:01
Jul  3 23:55:59 dnsmasq-dhcp[2867]: DHCPDISCOVER(eth0) 02:00:4b:c7:00:03 no address available
                
> [Automation] Basic Zone with SG - ip address are not getting assigned to VM
> ---------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3312
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3312
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation, Network Controller
>    Affects Versions: 4.2.0
>         Environment: KVM Basic Zone 
> Build from master-6-17-stable  branch 
>            Reporter: Rayees Namathponnan
>            Assignee: Jayapal Reddy
>            Priority: Blocker
>             Fix For: 4.2.0
>
>         Attachments: CLOUDSTACK-3312_dnsmasq_Logs.rar, CLOUDSTACK-3312.rar, dnsmasq.log
>
>
> Step 1 : Create basic zone on KVM 
> Step 2 : Create Security Group 
> Step 3 : Assing ingress rule port 22 
> Step 4 : Deploy new VM 
> Step 5 : Login to the VM 
> Actual Result :
> Failed to login to the VM; if you login to the VM from console proxy;  you can see IP
is not allocated for this VM 
> Work around 
> You need to restart dnsmasq service from router, and deploy new VM; then IPs are getting
assigned to VMs

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

Mime
View raw message