cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rayees Namathponnan (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 23:33:20 GMT

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

Rayees Namathponnan commented on CLOUDSTACK-3312:
-------------------------------------------------

1) Is it reproducing always ? 

Yes 

2)   Is it with the fresh setup or before creating VM did you destroyed some VMs

Yes, its fresh setup; before running automation we re-install server, clean up primary and
sec storage 

3) Attached  dnsmasq.leases

Created VM RysSG2 , In UI i can see ip address 10.223.250.227 allocated in NIC tab ; but i
cannot access access with this IP adress; 
Access this vm from console proxy;  ip not configured for this 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