[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-8005) try.steamcannon.org doesn't launch instances with the key that was indicated
Andre Dietisheim (JIRA)
jira-events at lists.jboss.org
Tue Dec 28 18:47:17 EST 2010
[ https://issues.jboss.org/browse/JBIDE-8005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andre Dietisheim updated JBIDE-8005:
------------------------------------
Summary: try.steamcannon.org doesn't launch instances with the key that was indicated (was: Deltacloud server doesn't report the key that was used to launch an instance)
Description:
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 instance that is launched on ec2 does not have any key indicated (the column "Key Pair Name" in aws is empty)
Try.steamcannon.org responds without a key in the response (<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
was:
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
> try.steamcannon.org doesn't launch instances with the key that was indicated
> ----------------------------------------------------------------------------
>
> Key: JBIDE-8005
> URL: https://issues.jboss.org/browse/JBIDE-8005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: deltacloud
> Affects Versions: 3.2.0.CR1
> Environment: deltacloud-core 0.1.2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 3.2.x
>
>
> 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 instance that is launched on ec2 does not have any key indicated (the column "Key Pair Name" in aws is empty)
> Try.steamcannon.org responds without a key in the response (<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
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list