[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7763) workflow is weird when it comes up to key management

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571812#comment-12571812 ] 

Andre Dietisheim commented on JBIDE-7763:
-----------------------------------------

DeltaCloudClient#listKeys is implemented.

Next step is to adapt the key management UI. It shall list server available keys instead of the keys that are available on the local filesys.

> workflow is weird when it comes up to key management
> ----------------------------------------------------
>
>                 Key: JBIDE-7763
>                 URL: https://issues.jboss.org/browse/JBIDE-7763
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: deltacloud
>    Affects Versions: 3.2.0.Beta2
>            Reporter: Andre Dietisheim
>            Assignee: Andre Dietisheim
>            Priority: Critical
>             Fix For: 3.2.0.CR1
>
>
> how to reproduce:
> 1) have a deltacloud instance with ec2 running
> 2) choose "Launch instance" in the Cloud view context menu
> 3) choose the image you want to launch an instance of
> 4) in the keys, hit "Manage"
> 5) browse to the dir where you stored the PEM file you recieved from amazon
> 6)  hit finish
> Result:
> You get an error dialog that tells you of an internal server error on the deltacloud server
> Expected result:
> instance could be launched
> Everything works fine if I create a new key or use a key I created within the deltacloud tools.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira