You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Abhinandan Prateek (JIRA)" <ji...@apache.org> on 2013/07/02 12:52:20 UTC

[jira] [Assigned] (CLOUDSTACK-3312) [Automation] Basic Zone with SG - ip address are not getting assigned to VM

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Abhinandan Prateek reassigned CLOUDSTACK-3312:
----------------------------------------------

    Assignee: Bharat Kumar
    
> [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: Bharat Kumar
>            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