cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayapal Reddy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3312) [Automation] Basic Zone with SG - ip address are not getting assigned to VM
Date Wed, 03 Jul 2013 11:01:20 GMT

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

Jayapal Reddy commented on CLOUDSTACK-3312:
-------------------------------------------

I figured out the issue.
The issue is with the dnsmasq.

VM is not getting ip address because the IP previously assigned to one of vm and vm is already
destroyed. 
The dnsmasq updated its dnsmasq.leases file. The dhcphosts.txt is also updated.

The dnsmasq cache has old mac and IP binding info.
So when new vm is requesting for the IP with new mac, it is saying the ip is already leased
to old mac.

Jul  3 10:43:55 dnsmasq-dhcp[2648]: not using configured address 10.223.250.227 because it
is leased to 06:00:0e:00:00:20


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