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

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

Github user kansal commented on the pull request:

    https://github.com/apache/cloudstack/pull/685#issuecomment-136250704
  
    @DaanHoogland Yes the first test in a way does the same thing only. The 
thing is that the second test is more intuitive in a way that it firsts 
registers a key-pair (the registration is successful) and then registers 
another one with different name but same key (Registration fails here). So the 
"Existing pair" check which the first one wants to test is automatically 
tested. In my opinion the first test can be removed. Your opinion? 


> 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