[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=12572302#comment-12572302 ] 

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

I currently hit what I believe is a bug in the server:

The server does not report the key that was used to create an instance.

I request the following when I create the instance (the key is set: keyname=ad):

http://try.steamcannon.org/deltacloud//api/instances?image_id=ami-7d07ec14&hwp_id=m1.small&realm_id=us-east-1a&name=gfdgs&hwp_memory=1740.8&hwp_storage=160&keyname=ad&commit=create

The server then responds without it (<keyname></keyname>):

<?xml version='1.0' encoding='utf-8' ?>
<instance href='http://try.steamcannon.org/deltacloud/api/instances/i-82a4b6ef' id='i-82a4b6ef'>
  <name>ami-7d07ec14</name>
  <owner_id>357159121505</owner_id>
  <image href='http://try.steamcannon.org/deltacloud/api/images/ami-7d07ec14' id='ami-7d07ec14'></image>
  <realm href='http://try.steamcannon.org/deltacloud/api/realms/us-east-1a' id='us-east-1a'></realm>
  <state>PENDING</state>
  <hardware_profile href='http://try.steamcannon.org/deltacloud/api/hardware_profiles/m1.small' id='m1.small'>
  </hardware_profile>
  <actions>
    <link href='http://try.steamcannon.org/deltacloud/api/instances/i-82a4b6ef/stop' method='post' rel='stop' />
  </actions>
  <launch_time>2010-12-25T14:42:22.000Z</launch_time>
  <public_addresses>
  </public_addresses>
  <private_addresses>
  </private_addresses>
  <authentication type='key'>
    <login>
      <keyname></keyname>
    </login>
  </authentication>
</instance>

I created a bug in the deltacloud jira: https://issues.apache.org/jira/browse/DTACLOUD-11

> 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