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 Tue, 02 Jul 2013 12:08:19 GMT

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

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

Please give more information on the below

1. Is it reproducing always ?

2. Is it with the fresh setup or before creating VM did you destroyed some VMs.
The reason is in community there are already discussion about lease of already assigned ip
will not be updated in dnsmasq.
Did you have below kind of logs in the vm.

dnsmasq-dhcp[pid]: not using configured address 192.168.1.100 because it is
leased to aa:bb:cc:11:22:33
dnsmasq-dhcp[pid]: DHCPDISCOVER(eth0) aa:bb:cc:22:33:44 no address available

3. Please attach the dnsmasq configuration files ( dnsmasq.leases) before and after deploying
vm
 
                
> [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.rar
>
>
> 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