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

Bharat Kumar commented on CLOUDSTACK-2953:
------------------------------------------

In case of ssh-key reset we have modified the script to fetch the public key 
using the name data-server instead of the eth0Ip of the router. So if some one 
wants to use this multiple ip ranges feature they will need to update the 
uservm templates with this modified ssh-key rest script. All VMs deployed prior 
to using this feature will be able to use the ssh-key reset with the old 
script.  The updating of the templates is required for the VMs which will be 
deployed in the new subnet. 
                
> [Multiple_IP_Ranges] VM does not get the public key from VR incase of 
> multiple subnets per vlan
> -----------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2953
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2953
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>         Environment: Setup: Basic zone with xen cluster
> Build: Laset master build
>            Reporter: Sanjeev N
>            Assignee: Bharat Kumar
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> VM does not get the public key from VR incase of multiple subnets per vlan
> Steps to Reproduce:
> ================
> 1.Bring up CS in basic zone with xen server
> 2.Add guest ip ranges in two CIDRs in the same vlan
> 3.Generate ssh key pair using follwoing api:
> http://10.147.59.119:8096/client/api?command=createSSHKeyPair&name=test2&account=admin&domainid=1
> 4.Register a template to CS which has ssh key reset script copied.
> 5.Deploy two guest vms with ip addresses from both the CIDRs with the key 
> pair generated above
> Expected Behavior:
> ===============
> In both the VM's authouried keys file should contain the public key and key 
> based access to vm should succeed.
> Actual Result:
> ============
> Guest vm deployed with ip address from first cidr able to fetch the public 
> key but not the other vm.
> Observations:
> ===========
> On VR web service is running on port 80 with ip address from the primary 
> subnet but not with the alias ip , hence fetching keys from the VR with alias 
> ip address failed.
> [root@ceddb099-8fee-462f-9520-c01b57762e4d ~]# wget 
> http://10.147.43.131/latest/public-keys
> --2013-06-12 10:02:49--  http://10.147.43.131/latest/public-keys
> Connecting to 10.147.43.131:80... failed: Connection refused.

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

Reply via email to