[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBIDE-8860) Key name is not displayed in Properties View

Andre Dietisheim (JIRA) jira-events at lists.jboss.org
Wed May 25 18:56:01 EDT 2011


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

Andre Dietisheim edited comment on JBIDE-8860 at 5/25/11 6:54 PM:
------------------------------------------------------------------

my current guess is that this is a bug in Deltacloud (server) 0.3.0:

If you list all instances you wont get the authentication bits for each instance whereas if you list a single instance you would get it:


* listing all instances:

{code}
<instances>
  <instance href='http://localhost:3001/api/instances/inst1' id='inst1'>
    <name>ddd</name>
    <owner_id>mockuser</owner_id>
    <image href='http://localhost:3001/api/images/img1' id='img1'></image>
    <realm href='http://localhost:3001/api/realms/us' id='us'></realm>
    <state>RUNNING</state>

    <hardware_profile href='http://localhost:3001/api/hardware_profiles/m1-xlarge' id='m1-xlarge'>
    </hardware_profile>
    <actions>
      <link href='http://localhost:3001/api/instances/inst1/reboot' method='post' rel='reboot' />
      <link href='http://localhost:3001/api/instances/inst1/stop' method='post' rel='stop' />
    </actions>
    <public_addresses>
      <address>img1.inst1.public.com</address>

    </public_addresses>
    <private_addresses>
      <address>img1.inst1.private.com</address>
    </private_addresses>
  </instance>
{code}

* listing a single instance:

{code}
<instance href='http://localhost:3001/api/instances/inst1' id='inst1'>
  <name>ddd</name>
  <owner_id>mockuser</owner_id>
  <image href='http://localhost:3001/api/images/img1' id='img1'></image>
  <realm href='http://localhost:3001/api/realms/us' id='us'></realm>
  <state>RUNNING</state>
  <hardware_profile href='http://localhost:3001/api/hardware_profiles/m1-xlarge' id='m1-xlarge'>

  </hardware_profile>
  <actions>
    <link href='http://localhost:3001/api/instances/inst1/reboot' method='post' rel='reboot' />
    <link href='http://localhost:3001/api/instances/inst1/stop' method='post' rel='stop' />
  </actions>
  <public_addresses>
    <address>img1.inst1.public.com</address>
  </public_addresses>

  <private_addresses>
    <address>img1.inst1.private.com</address>
  </private_addresses>
  <authentication type='key'>
    <login>
      <keyname></keyname>
    </login>
  </authentication>

</instance>
{code}

I reported this to the deltacloud dev-mailinglist and will act upon their answer.

      was (Author: adietish):
    my current guess is that this is a bug in Deltacloud (server) 0.3.0:

If you list all instances you wont get the authentication bits for each instance whereas if you list a single instance you would get it:


* listing all instances:

<instances>
  <instance href='http://localhost:3001/api/instances/inst1' id='inst1'>
    <name>ddd</name>
    <owner_id>mockuser</owner_id>
    <image href='http://localhost:3001/api/images/img1' id='img1'></image>
    <realm href='http://localhost:3001/api/realms/us' id='us'></realm>
    <state>RUNNING</state>

    <hardware_profile href='http://localhost:3001/api/hardware_profiles/m1-xlarge' id='m1-xlarge'>
    </hardware_profile>
    <actions>
      <link href='http://localhost:3001/api/instances/inst1/reboot' method='post' rel='reboot' />
      <link href='http://localhost:3001/api/instances/inst1/stop' method='post' rel='stop' />
    </actions>
    <public_addresses>
      <address>img1.inst1.public.com</address>

    </public_addresses>
    <private_addresses>
      <address>img1.inst1.private.com</address>
    </private_addresses>
  </instance>

* listing a single instance:

<instance href='http://localhost:3001/api/instances/inst1' id='inst1'>
  <name>ddd</name>
  <owner_id>mockuser</owner_id>
  <image href='http://localhost:3001/api/images/img1' id='img1'></image>
  <realm href='http://localhost:3001/api/realms/us' id='us'></realm>
  <state>RUNNING</state>
  <hardware_profile href='http://localhost:3001/api/hardware_profiles/m1-xlarge' id='m1-xlarge'>

  </hardware_profile>
  <actions>
    <link href='http://localhost:3001/api/instances/inst1/reboot' method='post' rel='reboot' />
    <link href='http://localhost:3001/api/instances/inst1/stop' method='post' rel='stop' />
  </actions>
  <public_addresses>
    <address>img1.inst1.public.com</address>
  </public_addresses>

  <private_addresses>
    <address>img1.inst1.private.com</address>
  </private_addresses>
  <authentication type='key'>
    <login>
      <keyname></keyname>
    </login>
  </authentication>

</instance>

I reported this to the deltacloud dev-mailinglist and will act upon their answer.
  
> Key name is not displayed in Properties View
> --------------------------------------------
>
>                 Key: JBIDE-8860
>                 URL: https://issues.jboss.org/browse/JBIDE-8860
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: deltacloud
>    Affects Versions: 3.2.1.M1
>            Reporter: Libor Zoubek
>            Assignee: Andre Dietisheim
>            Priority: Minor
>             Fix For: 3.2.x, 3.3.x
>
>
> Key name that was used to launch instance is not displayed in properties view. If I select another instance, which was not launched by me or deltacloud or our client I see 'null' instead of key name. If I select my instance I see nothing

--
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