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

ASF GitHub Bot commented on CLOUDSTACK-8727:
--------------------------------------------

GitHub user kansal opened a pull request:

    https://github.com/apache/cloudstack/pull/685

    CLOUDSTACK-8727: API call listVirtualMachines returns same keypair

    Currently the user can register same key with different names. Upon listing 
the VM's the name which got registered first is being returned and not the 
actual one. Anyhow this behavior is rare and not good. I have added a UNIQUE 
constraint on the ssh_keypairs table and also made sure that the previous 
registered keys(with duplicates) get deleted.  

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kansal/cloudstack CLOUDSTACK-8727

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/685.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #685
    
----
commit ee45f299f4df9b51ba3c530a9770392780a33dd5
Author: Kshitij Kansal <[email protected]>
Date:   2015-08-12T12:07:48Z

    CLOUDSTACK-8727: API call listVirtualMachines returns same keypair

----


> API call listVirtualMachines returns same keypair
> -------------------------------------------------
>
>                 Key: CLOUDSTACK-8727
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8727
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>            Reporter: Kshitij Kansal
>
> If you register 2 SSH keypairs with the same public key then 
> listVirtualMachines API call will only return the first keypair. Although its 
> a very rare case and generally don't make much sense by registering the same 
> key with different name, still it can be fixed. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to