You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Ronelle Landy (Created) (JIRA)" <ji...@apache.org> on 2012/03/27 22:46:28 UTC
[jira] [Created] (DTACLOUD-181) json output from creating an image
(from a stopped instance) in RHEV-M does not return readable hardware
profiles
json output from creating an image (from a stopped instance) in RHEV-M does not return readable hardware profiles
-----------------------------------------------------------------------------------------------------------------
Key: DTACLOUD-181
URL: https://issues.apache.org/jira/browse/DTACLOUD-181
Project: DeltaCloud
Issue Type: Bug
Components: Server
Environment: deltacloud commit version: 59659586a6783bd4c851056813ed8369d08d4589 - clone: from https://git-wip-us.apache.org/repos/asf/deltacloud.git
Fedora 16
rhevm 3.X
Reporter: Ronelle Landy
Assignee: David Lutterkort
Priority: Minor
Found when verifying DTACLOUD-170:
The json output from creating an image from a STOPPED instance in rhevm returns the hardware profiles as:
#<Deltacloud::HardwareProfile:0x7fa438754db8>
The XML output from the same operation returns the hardware profiles as:
<hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
The complete output in both json and xml are copied below. Logging this as a sepate issue to DTACLOUD-170 as it is far more minor.
>> Output in json
curl -X POST -F "name=rlandyImage" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=json"
{"image":{"owner_id":"xxx","href":"http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/c4ddf46e-3abb-4bce-962e-2b55d4a01594","actions":[{"create_instance":{"method":"post","href":"/api/instances;image_id=c4ddf46e-3abb-4bce-962e-2b55d4a01594"}}],"architecture":"x86_64","state":"\n locked\n ","name":"rlandyImage","id":"c4ddf46e-3abb-4bce-962e-2b55d4a01594","description":"Image description","hardware_profiles":["#<Deltacloud::HardwareProfile:0x7fa438758288>","#<Deltacloud::HardwareProfile:0x7fa438754db8>"]}}[rlandy@localhost /]$
[rlandy@localhost /]$
>> Output in xml
[rlandy@localhost /]$ curl -X POST -F "name=rlandyImageXml" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=xml"
<?xml version='1.0' encoding='utf-8' ?>
<image href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' id='9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f'>
<name>rlandyImageXml</name>
<owner_id>xxx</owner_id>
<description>Image description</description>
<architecture>x86_64</architecture>
<state>locked</state>
<hardware_profiles>
<hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
<hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/DESKTOP' id='DESKTOP' rel='hardware_profile'></hardware_profile>
</hardware_profiles>
<actions>
<link href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/instances;image_id=9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' method='post' rel='create_instance' />
</actions>
</image>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DTACLOUD-181) json output from creating an
image (from a stopped instance) in RHEV-M does not return readable hardware
profiles
Posted by "Marios Andreou (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240339#comment-13240339 ]
Marios Andreou commented on DTACLOUD-181:
-----------------------------------------
pushed to master:
commit bd67983cac800cec97e4ff5aa0b3ac491452a2f7
Author: marios <ma...@redhat.com>
Date: Wed Mar 28 12:18:02 2012 +0300
Fixes DTACLOUD_181: json output of 'HardareProfile' within an 'Image' object
https://issues.apache.org/jira/browse/DTACLOUD-181
Marking as resolved.
> json output from creating an image (from a stopped instance) in RHEV-M does not return readable hardware profiles
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-181
> URL: https://issues.apache.org/jira/browse/DTACLOUD-181
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud commit version: 59659586a6783bd4c851056813ed8369d08d4589 - clone: from https://git-wip-us.apache.org/repos/asf/deltacloud.git
> Fedora 16
> rhevm 3.X
> Reporter: Ronelle Landy
> Assignee: Ronelle Landy
> Priority: Minor
> Attachments: 0001-Fixes-DTACLOUD_181-json-output-of-HardareProfile-wit.patch
>
>
> Found when verifying DTACLOUD-170:
> The json output from creating an image from a STOPPED instance in rhevm returns the hardware profiles as:
> #<Deltacloud::HardwareProfile:0x7fa438754db8>
> The XML output from the same operation returns the hardware profiles as:
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> The complete output in both json and xml are copied below. Logging this as a sepate issue to DTACLOUD-170 as it is far more minor.
> >> Output in json
> curl -X POST -F "name=rlandyImage" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=json"
> {"image":{"owner_id":"xxx","href":"http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/c4ddf46e-3abb-4bce-962e-2b55d4a01594","actions":[{"create_instance":{"method":"post","href":"/api/instances;image_id=c4ddf46e-3abb-4bce-962e-2b55d4a01594"}}],"architecture":"x86_64","state":"\n locked\n ","name":"rlandyImage","id":"c4ddf46e-3abb-4bce-962e-2b55d4a01594","description":"Image description","hardware_profiles":["#<Deltacloud::HardwareProfile:0x7fa438758288>","#<Deltacloud::HardwareProfile:0x7fa438754db8>"]}}[rlandy@localhost /]$
> [rlandy@localhost /]$
> >> Output in xml
> [rlandy@localhost /]$ curl -X POST -F "name=rlandyImageXml" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=xml"
> <?xml version='1.0' encoding='utf-8' ?>
> <image href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' id='9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f'>
> <name>rlandyImageXml</name>
> <owner_id>xxx</owner_id>
> <description>Image description</description>
> <architecture>x86_64</architecture>
> <state>locked</state>
> <hardware_profiles>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/DESKTOP' id='DESKTOP' rel='hardware_profile'></hardware_profile>
> </hardware_profiles>
> <actions>
> <link href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/instances;image_id=9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' method='post' rel='create_instance' />
> </actions>
> </image>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DTACLOUD-181) json output from creating an
image (from a stopped instance) in RHEV-M does not return readable hardware
profiles
Posted by "Michal Fojtik (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240332#comment-13240332 ]
Michal Fojtik commented on DTACLOUD-181:
----------------------------------------
ACK. Looks good to me. Feel free to push it.
> json output from creating an image (from a stopped instance) in RHEV-M does not return readable hardware profiles
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-181
> URL: https://issues.apache.org/jira/browse/DTACLOUD-181
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud commit version: 59659586a6783bd4c851056813ed8369d08d4589 - clone: from https://git-wip-us.apache.org/repos/asf/deltacloud.git
> Fedora 16
> rhevm 3.X
> Reporter: Ronelle Landy
> Assignee: Marios Andreou
> Priority: Minor
> Attachments: 0001-Fixes-DTACLOUD_181-json-output-of-HardareProfile-wit.patch
>
>
> Found when verifying DTACLOUD-170:
> The json output from creating an image from a STOPPED instance in rhevm returns the hardware profiles as:
> #<Deltacloud::HardwareProfile:0x7fa438754db8>
> The XML output from the same operation returns the hardware profiles as:
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> The complete output in both json and xml are copied below. Logging this as a sepate issue to DTACLOUD-170 as it is far more minor.
> >> Output in json
> curl -X POST -F "name=rlandyImage" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=json"
> {"image":{"owner_id":"xxx","href":"http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/c4ddf46e-3abb-4bce-962e-2b55d4a01594","actions":[{"create_instance":{"method":"post","href":"/api/instances;image_id=c4ddf46e-3abb-4bce-962e-2b55d4a01594"}}],"architecture":"x86_64","state":"\n locked\n ","name":"rlandyImage","id":"c4ddf46e-3abb-4bce-962e-2b55d4a01594","description":"Image description","hardware_profiles":["#<Deltacloud::HardwareProfile:0x7fa438758288>","#<Deltacloud::HardwareProfile:0x7fa438754db8>"]}}[rlandy@localhost /]$
> [rlandy@localhost /]$
> >> Output in xml
> [rlandy@localhost /]$ curl -X POST -F "name=rlandyImageXml" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=xml"
> <?xml version='1.0' encoding='utf-8' ?>
> <image href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' id='9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f'>
> <name>rlandyImageXml</name>
> <owner_id>xxx</owner_id>
> <description>Image description</description>
> <architecture>x86_64</architecture>
> <state>locked</state>
> <hardware_profiles>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/DESKTOP' id='DESKTOP' rel='hardware_profile'></hardware_profile>
> </hardware_profiles>
> <actions>
> <link href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/instances;image_id=9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' method='post' rel='create_instance' />
> </actions>
> </image>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (DTACLOUD-181) json output from creating an image
(from a stopped instance) in RHEV-M does not return readable hardware
profiles
Posted by "Ronelle Landy (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ronelle Landy reassigned DTACLOUD-181:
--------------------------------------
Assignee: Ronelle Landy (was: Marios Andreou)
> json output from creating an image (from a stopped instance) in RHEV-M does not return readable hardware profiles
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-181
> URL: https://issues.apache.org/jira/browse/DTACLOUD-181
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud commit version: 59659586a6783bd4c851056813ed8369d08d4589 - clone: from https://git-wip-us.apache.org/repos/asf/deltacloud.git
> Fedora 16
> rhevm 3.X
> Reporter: Ronelle Landy
> Assignee: Ronelle Landy
> Priority: Minor
> Attachments: 0001-Fixes-DTACLOUD_181-json-output-of-HardareProfile-wit.patch
>
>
> Found when verifying DTACLOUD-170:
> The json output from creating an image from a STOPPED instance in rhevm returns the hardware profiles as:
> #<Deltacloud::HardwareProfile:0x7fa438754db8>
> The XML output from the same operation returns the hardware profiles as:
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> The complete output in both json and xml are copied below. Logging this as a sepate issue to DTACLOUD-170 as it is far more minor.
> >> Output in json
> curl -X POST -F "name=rlandyImage" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=json"
> {"image":{"owner_id":"xxx","href":"http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/c4ddf46e-3abb-4bce-962e-2b55d4a01594","actions":[{"create_instance":{"method":"post","href":"/api/instances;image_id=c4ddf46e-3abb-4bce-962e-2b55d4a01594"}}],"architecture":"x86_64","state":"\n locked\n ","name":"rlandyImage","id":"c4ddf46e-3abb-4bce-962e-2b55d4a01594","description":"Image description","hardware_profiles":["#<Deltacloud::HardwareProfile:0x7fa438758288>","#<Deltacloud::HardwareProfile:0x7fa438754db8>"]}}[rlandy@localhost /]$
> [rlandy@localhost /]$
> >> Output in xml
> [rlandy@localhost /]$ curl -X POST -F "name=rlandyImageXml" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=xml"
> <?xml version='1.0' encoding='utf-8' ?>
> <image href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' id='9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f'>
> <name>rlandyImageXml</name>
> <owner_id>xxx</owner_id>
> <description>Image description</description>
> <architecture>x86_64</architecture>
> <state>locked</state>
> <hardware_profiles>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/DESKTOP' id='DESKTOP' rel='hardware_profile'></hardware_profile>
> </hardware_profiles>
> <actions>
> <link href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/instances;image_id=9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' method='post' rel='create_instance' />
> </actions>
> </image>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DTACLOUD-181) json output from creating an image
(from a stopped instance) in RHEV-M does not return readable hardware
profiles
Posted by "Marios Andreou (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marios Andreou resolved DTACLOUD-181.
-------------------------------------
Resolution: Fixed
> json output from creating an image (from a stopped instance) in RHEV-M does not return readable hardware profiles
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-181
> URL: https://issues.apache.org/jira/browse/DTACLOUD-181
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud commit version: 59659586a6783bd4c851056813ed8369d08d4589 - clone: from https://git-wip-us.apache.org/repos/asf/deltacloud.git
> Fedora 16
> rhevm 3.X
> Reporter: Ronelle Landy
> Assignee: Ronelle Landy
> Priority: Minor
> Attachments: 0001-Fixes-DTACLOUD_181-json-output-of-HardareProfile-wit.patch
>
>
> Found when verifying DTACLOUD-170:
> The json output from creating an image from a STOPPED instance in rhevm returns the hardware profiles as:
> #<Deltacloud::HardwareProfile:0x7fa438754db8>
> The XML output from the same operation returns the hardware profiles as:
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> The complete output in both json and xml are copied below. Logging this as a sepate issue to DTACLOUD-170 as it is far more minor.
> >> Output in json
> curl -X POST -F "name=rlandyImage" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=json"
> {"image":{"owner_id":"xxx","href":"http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/c4ddf46e-3abb-4bce-962e-2b55d4a01594","actions":[{"create_instance":{"method":"post","href":"/api/instances;image_id=c4ddf46e-3abb-4bce-962e-2b55d4a01594"}}],"architecture":"x86_64","state":"\n locked\n ","name":"rlandyImage","id":"c4ddf46e-3abb-4bce-962e-2b55d4a01594","description":"Image description","hardware_profiles":["#<Deltacloud::HardwareProfile:0x7fa438758288>","#<Deltacloud::HardwareProfile:0x7fa438754db8>"]}}[rlandy@localhost /]$
> [rlandy@localhost /]$
> >> Output in xml
> [rlandy@localhost /]$ curl -X POST -F "name=rlandyImageXml" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=xml"
> <?xml version='1.0' encoding='utf-8' ?>
> <image href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' id='9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f'>
> <name>rlandyImageXml</name>
> <owner_id>xxx</owner_id>
> <description>Image description</description>
> <architecture>x86_64</architecture>
> <state>locked</state>
> <hardware_profiles>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/DESKTOP' id='DESKTOP' rel='hardware_profile'></hardware_profile>
> </hardware_profiles>
> <actions>
> <link href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/instances;image_id=9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' method='post' rel='create_instance' />
> </actions>
> </image>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DTACLOUD-181) json output from creating an
image (from a stopped instance) in RHEV-M does not return readable hardware
profiles
Posted by "Marios Andreou (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240316#comment-13240316 ]
Marios Andreou commented on DTACLOUD-181:
-----------------------------------------
Issue is verified and reproducible. The issue is specific to the listing of hardware_profiles within an Image, but is not confined to the rhevm driver (I could also reproduce with ec2 driver for example). An easier reproducer is to simply GET a specific Image with json format:
curl --user "user:pass" http://localhost:3001/api/images/88ead4c9-3488-4f2b-87fb-1cc1d70b65ca?format=json
With the attached patch applied output looks like:
{"image":{"actions":[{"create_instance":{"href":"/api/instances;image_id=88ead4c9-3488-4f2b-87fb-1cc1d70b65ca","method":"post"}}],"href":"http://localhost:3001/api/images/88ead4c9-3488-4f2b-87fb-1cc1d70b65ca","architecture":"x86_64","state":"\n ok\n ","description":"","hardware_profiles":[{"SERVER":{"href":"http://localhost:3001/api/hardware_profiles/SERVER"}},{"DESKTOP":{"href":"http://localhost:3001/api/hardware_profiles/DESKTOP"}}],"name":"test1","id":"88ead4c9-3488-4f2b-87fb-1cc1d70b65ca","owner_id":"admin@internal"}}
i.e. "hardware_profiles": [ {"hwp1_name": {"href":"uri_for_hwp1"}}, {"hwp2_name": {"href":"uri_for_hwp2"}} ]
consistent with the xml output, we provide name and ref to each hwp compatible with the given image.
Waiting for review before pushing patch to master.
> json output from creating an image (from a stopped instance) in RHEV-M does not return readable hardware profiles
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-181
> URL: https://issues.apache.org/jira/browse/DTACLOUD-181
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud commit version: 59659586a6783bd4c851056813ed8369d08d4589 - clone: from https://git-wip-us.apache.org/repos/asf/deltacloud.git
> Fedora 16
> rhevm 3.X
> Reporter: Ronelle Landy
> Assignee: Marios Andreou
> Priority: Minor
> Attachments: 0001-Fixes-DTACLOUD_181-json-output-of-HardareProfile-wit.patch
>
>
> Found when verifying DTACLOUD-170:
> The json output from creating an image from a STOPPED instance in rhevm returns the hardware profiles as:
> #<Deltacloud::HardwareProfile:0x7fa438754db8>
> The XML output from the same operation returns the hardware profiles as:
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> The complete output in both json and xml are copied below. Logging this as a sepate issue to DTACLOUD-170 as it is far more minor.
> >> Output in json
> curl -X POST -F "name=rlandyImage" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=json"
> {"image":{"owner_id":"xxx","href":"http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/c4ddf46e-3abb-4bce-962e-2b55d4a01594","actions":[{"create_instance":{"method":"post","href":"/api/instances;image_id=c4ddf46e-3abb-4bce-962e-2b55d4a01594"}}],"architecture":"x86_64","state":"\n locked\n ","name":"rlandyImage","id":"c4ddf46e-3abb-4bce-962e-2b55d4a01594","description":"Image description","hardware_profiles":["#<Deltacloud::HardwareProfile:0x7fa438758288>","#<Deltacloud::HardwareProfile:0x7fa438754db8>"]}}[rlandy@localhost /]$
> [rlandy@localhost /]$
> >> Output in xml
> [rlandy@localhost /]$ curl -X POST -F "name=rlandyImageXml" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=xml"
> <?xml version='1.0' encoding='utf-8' ?>
> <image href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' id='9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f'>
> <name>rlandyImageXml</name>
> <owner_id>xxx</owner_id>
> <description>Image description</description>
> <architecture>x86_64</architecture>
> <state>locked</state>
> <hardware_profiles>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/DESKTOP' id='DESKTOP' rel='hardware_profile'></hardware_profile>
> </hardware_profiles>
> <actions>
> <link href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/instances;image_id=9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' method='post' rel='create_instance' />
> </actions>
> </image>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DTACLOUD-181) json output from creating an
image (from a stopped instance) in RHEV-M does not return readable hardware
profiles
Posted by "Ronelle Landy (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240494#comment-13240494 ]
Ronelle Landy commented on DTACLOUD-181:
----------------------------------------
Tested deltacloud git commit version: bd67983cac800cec97e4ff5aa0b3ac491452a2f7 - branch 'master' of https://git-wip-us.apache.org/repos/asf/deltacloud
Now, using json or xml output, when creating an image with parameters instance_id, name and description, a 500 backend error is returned:
curl -X POST -F "name=rlandyImage" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://localhost:4007/api/images?format=xml"
<?xml version='1.0' encoding='utf-8' ?>
<error status='500' url='/api/images?format=xml'>
<kind>backend_error</kind>
<backend driver='rhevm' provider='https://qeblade26.rhq.lab.eng.bos.redhat.com:8443/api;4051216f-a778-488f-8ae4-5a2541b009ff'>
<code>500</code>
</backend>
<message><![CDATA[Unhandled exception or status code (wrong number of arguments (2 for 1))]]></message>
<backtrace>
<![CDATA[/home/rlandy/workspace/deltacloud/server/lib/deltacloud/drivers/rhevm/rhevm_driver.rb:113:in `create_template'
/home/rlandy/workspace/deltacloud/server/lib/deltacloud/drivers/rhevm/rhevm_driver.rb:113:in `create_image'
/home/rlandy/workspace/deltacloud/server/lib/deltacloud/base_driver/exceptions.rb:173:in `call'
/home/rlandy/workspace/deltacloud/server/lib/deltacloud/base_driver/exceptions.rb:173:in `safely'
/home/rlandy/workspace/deltacloud/server/lib/deltacloud/drivers/rhevm/rhevm_driver.rb:112:in `create_image'
/home/rlandy/workspace/deltacloud/server/lib/deltacloud/server.rb:258
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rabbit.rb:125:in `instance_eval'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rabbit.rb:125:in `POST /api/images'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:1211:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:1211:in `compile!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:772:in `[]'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:772:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:788:in `route_eval'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:772:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:821:in `process_route'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:819:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:819:in `process_route'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:771:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:770:in `each'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:770:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:886:in `dispatch!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:706:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:871:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:706:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:692:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/commonlogger.rb:20:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_date.rb:31:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_accept.rb:152:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/showexceptions.rb:21:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_driver_select.rb:45:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_matrix_params.rb:106:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_runtime.rb:36:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_etag.rb:41:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.4/lib/rack/accept/context.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/logger.rb:15:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/commonlogger.rb:20:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/methodoverride.rb:24:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:1334:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:1403:in `synchronize'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:1334:in `call'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:80:in `pre_process'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:78:in `catch'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:78:in `pre_process'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1060:in `call'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1060:in `spawn_threadpool'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `initialize'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `new'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `spawn_threadpool'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1049:in `defer'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:50:in `process'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:38:in `receive_data'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run_machine'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/backends/base.rb:61:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/server.rb:159:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/controllers/controller.rb:86:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/runner.rb:185:in `send'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/runner.rb:185:in `run_command'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/runner.rb:151:in `run!'
./bin/deltacloudd:239]]>
</backtrace>
<request>
<param name='name'>rlandyImage</param>
<param name='description'>Image description</param>
<param name='captures'>Deltacloud::ExceptionHandler::BackendError</param>
<param name='instance_id'>59f35d07-093c-46a5-814b-d0c6084ef8c9</param>
<param name='format'>xml</param>
</request>
</error>
Using just the instance_id parameter returns 'specified instance not found' ... Note that the output below shows, first a GET of that instance, and then the image creation error:
[rlandy@localhost /]$ curl -X GET --user "uname:password" "http://localhost:4007/api/instances/59f35d07-093c-46a5-814b-d0c6084ef8c9?format=xml" <?xml version='1.0' encoding='utf-8' ?>
<instance href='http://localhost:4007/api/instances/59f35d07-093c-46a5-814b-d0c6084ef8c9' id='59f35d07-093c-46a5-814b-d0c6084ef8c9'>
<name>dajo-237-myDevRhel61</name>
<owner_id>admin@internal</owner_id>
<image href='http://localhost:4007/api/images/3ba703ba-4f5b-4725-8597-eb0d473d9c33' id='3ba703ba-4f5b-4725-8597-eb0d473d9c33'></image>
<realm href='http://localhost:4007/api/realms/ba2b3a52-4303-11e1-b6c2-5cf3fc1c861c' id='ba2b3a52-4303-11e1-b6c2-5cf3fc1c861c'></realm>
<state>STOPPED</state>
<hardware_profile href='http://localhost:4007/api/hardware_profiles/SERVER' id='SERVER'>
<property kind='fixed' name='memory' unit='MB' value='512'></property>
<property kind='fixed' name='cpu' unit='count' value='1'></property>
<property kind='fixed' name='storage' unit='GB' value='1'></property>
</hardware_profile>
<actions>
<link href='http://localhost:4007/api/instances/59f35d07-093c-46a5-814b-d0c6084ef8c9/start' method='post' rel='start' />
<link href='http://localhost:4007/api/instances/59f35d07-093c-46a5-814b-d0c6084ef8c9' method='delete' rel='destroy' />
<link href='http://localhost:4007/api/images;instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9' method='post' rel='create_image' />
</actions>
<launch_time>2012-03-27T14:21:39.007-04:00</launch_time>
<public_addresses><address type='mac'>00:1a:4a:10:78:5b</address>
<address port='5908' type='vnc'>qeblade27.rhq.lab.eng.bos.redhat.com</address></public_addresses>
<private_addresses></private_addresses>
</instance>
[rlandy@localhost /]$ curl -X POST -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://localhost:4007/api/images?format=xml"
<?xml version='1.0' encoding='utf-8' ?>
<error status='500' url='/api/images?format=xml'>
<kind>backend_error</kind>
<backend driver='rhevm' provider='https://qeblade26.rhq.lab.eng.bos.redhat.com:8443/api;4051216f-a778-488f-8ae4-5a2541b009ff'>
<code>500</code>
</backend>
<message><![CDATA[Specified instance '59f35d07-093c-46a5-814b-d0c6084ef8c9' not found]]></message>
<backtrace>
<![CDATA[/home/rlandy/workspace/deltacloud/server/lib/deltacloud/drivers/rhevm/rhevm_driver.rb:109:in `create_image'
/home/rlandy/workspace/deltacloud/server/lib/deltacloud/server.rb:258
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rabbit.rb:125:in `instance_eval'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rabbit.rb:125:in `POST /api/images'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:1211:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:1211:in `compile!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:772:in `[]'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:772:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:788:in `route_eval'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:772:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:821:in `process_route'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:819:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:819:in `process_route'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:771:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:770:in `each'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:770:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:886:in `dispatch!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:706:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:871:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:706:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:692:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/commonlogger.rb:20:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_date.rb:31:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_accept.rb:152:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/showexceptions.rb:21:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_driver_select.rb:45:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_matrix_params.rb:106:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_runtime.rb:36:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_etag.rb:41:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.4/lib/rack/accept/context.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/logger.rb:15:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/commonlogger.rb:20:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/methodoverride.rb:24:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:1334:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:1403:in `synchronize'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:1334:in `call'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:80:in `pre_process'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:78:in `catch'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:78:in `pre_process'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1060:in `call'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1060:in `spawn_threadpool'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `initialize'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `new'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `spawn_threadpool'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1049:in `defer'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:50:in `process'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:38:in `receive_data'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run_machine'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/backends/base.rb:61:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/server.rb:159:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/controllers/controller.rb:86:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/runner.rb:185:in `send'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/runner.rb:185:in `run_command'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/runner.rb:151:in `run!'
./bin/deltacloudd:239]]>
</backtrace>
<request>
<param name='captures'>Specified instance '59f35d07-093c-46a5-814b-d0c6084ef8c9' not found</param>
<param name='instance_id'>59f35d07-093c-46a5-814b-d0c6084ef8c9</param>
<param name='format'>xml</param>
</request>
</error>
> json output from creating an image (from a stopped instance) in RHEV-M does not return readable hardware profiles
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-181
> URL: https://issues.apache.org/jira/browse/DTACLOUD-181
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud commit version: 59659586a6783bd4c851056813ed8369d08d4589 - clone: from https://git-wip-us.apache.org/repos/asf/deltacloud.git
> Fedora 16
> rhevm 3.X
> Reporter: Ronelle Landy
> Assignee: Ronelle Landy
> Priority: Minor
> Attachments: 0001-Fixes-DTACLOUD_181-json-output-of-HardareProfile-wit.patch
>
>
> Found when verifying DTACLOUD-170:
> The json output from creating an image from a STOPPED instance in rhevm returns the hardware profiles as:
> #<Deltacloud::HardwareProfile:0x7fa438754db8>
> The XML output from the same operation returns the hardware profiles as:
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> The complete output in both json and xml are copied below. Logging this as a sepate issue to DTACLOUD-170 as it is far more minor.
> >> Output in json
> curl -X POST -F "name=rlandyImage" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=json"
> {"image":{"owner_id":"xxx","href":"http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/c4ddf46e-3abb-4bce-962e-2b55d4a01594","actions":[{"create_instance":{"method":"post","href":"/api/instances;image_id=c4ddf46e-3abb-4bce-962e-2b55d4a01594"}}],"architecture":"x86_64","state":"\n locked\n ","name":"rlandyImage","id":"c4ddf46e-3abb-4bce-962e-2b55d4a01594","description":"Image description","hardware_profiles":["#<Deltacloud::HardwareProfile:0x7fa438758288>","#<Deltacloud::HardwareProfile:0x7fa438754db8>"]}}[rlandy@localhost /]$
> [rlandy@localhost /]$
> >> Output in xml
> [rlandy@localhost /]$ curl -X POST -F "name=rlandyImageXml" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=xml"
> <?xml version='1.0' encoding='utf-8' ?>
> <image href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' id='9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f'>
> <name>rlandyImageXml</name>
> <owner_id>xxx</owner_id>
> <description>Image description</description>
> <architecture>x86_64</architecture>
> <state>locked</state>
> <hardware_profiles>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/DESKTOP' id='DESKTOP' rel='hardware_profile'></hardware_profile>
> </hardware_profiles>
> <actions>
> <link href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/instances;image_id=9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' method='post' rel='create_instance' />
> </actions>
> </image>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (DTACLOUD-181) json output from creating an image
(from a stopped instance) in RHEV-M does not return readable hardware
profiles
Posted by "Marios Andreou (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marios Andreou reassigned DTACLOUD-181:
---------------------------------------
Assignee: Ronelle Landy (was: Marios Andreou)
> json output from creating an image (from a stopped instance) in RHEV-M does not return readable hardware profiles
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-181
> URL: https://issues.apache.org/jira/browse/DTACLOUD-181
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud commit version: 59659586a6783bd4c851056813ed8369d08d4589 - clone: from https://git-wip-us.apache.org/repos/asf/deltacloud.git
> Fedora 16
> rhevm 3.X
> Reporter: Ronelle Landy
> Assignee: Ronelle Landy
> Priority: Minor
> Attachments: 0001-Fixes-DTACLOUD_181-json-output-of-HardareProfile-wit.patch
>
>
> Found when verifying DTACLOUD-170:
> The json output from creating an image from a STOPPED instance in rhevm returns the hardware profiles as:
> #<Deltacloud::HardwareProfile:0x7fa438754db8>
> The XML output from the same operation returns the hardware profiles as:
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> The complete output in both json and xml are copied below. Logging this as a sepate issue to DTACLOUD-170 as it is far more minor.
> >> Output in json
> curl -X POST -F "name=rlandyImage" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=json"
> {"image":{"owner_id":"xxx","href":"http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/c4ddf46e-3abb-4bce-962e-2b55d4a01594","actions":[{"create_instance":{"method":"post","href":"/api/instances;image_id=c4ddf46e-3abb-4bce-962e-2b55d4a01594"}}],"architecture":"x86_64","state":"\n locked\n ","name":"rlandyImage","id":"c4ddf46e-3abb-4bce-962e-2b55d4a01594","description":"Image description","hardware_profiles":["#<Deltacloud::HardwareProfile:0x7fa438758288>","#<Deltacloud::HardwareProfile:0x7fa438754db8>"]}}[rlandy@localhost /]$
> [rlandy@localhost /]$
> >> Output in xml
> [rlandy@localhost /]$ curl -X POST -F "name=rlandyImageXml" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=xml"
> <?xml version='1.0' encoding='utf-8' ?>
> <image href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' id='9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f'>
> <name>rlandyImageXml</name>
> <owner_id>xxx</owner_id>
> <description>Image description</description>
> <architecture>x86_64</architecture>
> <state>locked</state>
> <hardware_profiles>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/DESKTOP' id='DESKTOP' rel='hardware_profile'></hardware_profile>
> </hardware_profiles>
> <actions>
> <link href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/instances;image_id=9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' method='post' rel='create_instance' />
> </actions>
> </image>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DTACLOUD-181) json output from creating an
image (from a stopped instance) in RHEV-M does not return readable hardware
profiles
Posted by "Ronelle Landy (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240536#comment-13240536 ]
Ronelle Landy commented on DTACLOUD-181:
----------------------------------------
Please ignore comments above ... local branch was not correctly merged with master.
Fixed with git commit bd67983cac800cec97e4ff5aa0b3ac491452a2f7 - clone: from https://git-wip-us.apache.org/repos/asf/deltacloud.git
curl -X POST -F "name=rlandyImage" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://localhost:4007/api/images?format=json"
{"image":{"owner_id":"admin@internal","href":"http://localhost:4007/api/images/5e6c4c39-bd85-4536-8b96-c4a0b9e260b4","actions":[{"create_instance":{"method":"post","href":"/api/instances;image_id=5e6c4c39-bd85-4536-8b96-c4a0b9e260b4"}}],"architecture":"x86_64","state":"\n locked\n ","name":"rlandyImage","id":"5e6c4c39-bd85-4536-8b96-c4a0b9e260b4","hardware_profiles":[{"SERVER":{"href":"http://localhost:4007/api/hardware_profiles/SERVER"}},{"DESKTOP":{"href":"http://localhost:4007/api/hardware_profiles/DESKTOP"}}],"description":"Image description"}}
> json output from creating an image (from a stopped instance) in RHEV-M does not return readable hardware profiles
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-181
> URL: https://issues.apache.org/jira/browse/DTACLOUD-181
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud commit version: 59659586a6783bd4c851056813ed8369d08d4589 - clone: from https://git-wip-us.apache.org/repos/asf/deltacloud.git
> Fedora 16
> rhevm 3.X
> Reporter: Ronelle Landy
> Assignee: Ronelle Landy
> Priority: Minor
> Attachments: 0001-Fixes-DTACLOUD_181-json-output-of-HardareProfile-wit.patch
>
>
> Found when verifying DTACLOUD-170:
> The json output from creating an image from a STOPPED instance in rhevm returns the hardware profiles as:
> #<Deltacloud::HardwareProfile:0x7fa438754db8>
> The XML output from the same operation returns the hardware profiles as:
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> The complete output in both json and xml are copied below. Logging this as a sepate issue to DTACLOUD-170 as it is far more minor.
> >> Output in json
> curl -X POST -F "name=rlandyImage" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=json"
> {"image":{"owner_id":"xxx","href":"http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/c4ddf46e-3abb-4bce-962e-2b55d4a01594","actions":[{"create_instance":{"method":"post","href":"/api/instances;image_id=c4ddf46e-3abb-4bce-962e-2b55d4a01594"}}],"architecture":"x86_64","state":"\n locked\n ","name":"rlandyImage","id":"c4ddf46e-3abb-4bce-962e-2b55d4a01594","description":"Image description","hardware_profiles":["#<Deltacloud::HardwareProfile:0x7fa438758288>","#<Deltacloud::HardwareProfile:0x7fa438754db8>"]}}[rlandy@localhost /]$
> [rlandy@localhost /]$
> >> Output in xml
> [rlandy@localhost /]$ curl -X POST -F "name=rlandyImageXml" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=xml"
> <?xml version='1.0' encoding='utf-8' ?>
> <image href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' id='9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f'>
> <name>rlandyImageXml</name>
> <owner_id>xxx</owner_id>
> <description>Image description</description>
> <architecture>x86_64</architecture>
> <state>locked</state>
> <hardware_profiles>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/DESKTOP' id='DESKTOP' rel='hardware_profile'></hardware_profile>
> </hardware_profiles>
> <actions>
> <link href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/instances;image_id=9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' method='post' rel='create_instance' />
> </actions>
> </image>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (DTACLOUD-181) json output from creating an image
(from a stopped instance) in RHEV-M does not return readable hardware
profiles
Posted by "Marios Andreou (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marios Andreou reassigned DTACLOUD-181:
---------------------------------------
Assignee: Marios Andreou (was: David Lutterkort)
> json output from creating an image (from a stopped instance) in RHEV-M does not return readable hardware profiles
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-181
> URL: https://issues.apache.org/jira/browse/DTACLOUD-181
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud commit version: 59659586a6783bd4c851056813ed8369d08d4589 - clone: from https://git-wip-us.apache.org/repos/asf/deltacloud.git
> Fedora 16
> rhevm 3.X
> Reporter: Ronelle Landy
> Assignee: Marios Andreou
> Priority: Minor
>
> Found when verifying DTACLOUD-170:
> The json output from creating an image from a STOPPED instance in rhevm returns the hardware profiles as:
> #<Deltacloud::HardwareProfile:0x7fa438754db8>
> The XML output from the same operation returns the hardware profiles as:
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> The complete output in both json and xml are copied below. Logging this as a sepate issue to DTACLOUD-170 as it is far more minor.
> >> Output in json
> curl -X POST -F "name=rlandyImage" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=json"
> {"image":{"owner_id":"xxx","href":"http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/c4ddf46e-3abb-4bce-962e-2b55d4a01594","actions":[{"create_instance":{"method":"post","href":"/api/instances;image_id=c4ddf46e-3abb-4bce-962e-2b55d4a01594"}}],"architecture":"x86_64","state":"\n locked\n ","name":"rlandyImage","id":"c4ddf46e-3abb-4bce-962e-2b55d4a01594","description":"Image description","hardware_profiles":["#<Deltacloud::HardwareProfile:0x7fa438758288>","#<Deltacloud::HardwareProfile:0x7fa438754db8>"]}}[rlandy@localhost /]$
> [rlandy@localhost /]$
> >> Output in xml
> [rlandy@localhost /]$ curl -X POST -F "name=rlandyImageXml" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=xml"
> <?xml version='1.0' encoding='utf-8' ?>
> <image href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' id='9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f'>
> <name>rlandyImageXml</name>
> <owner_id>xxx</owner_id>
> <description>Image description</description>
> <architecture>x86_64</architecture>
> <state>locked</state>
> <hardware_profiles>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/DESKTOP' id='DESKTOP' rel='hardware_profile'></hardware_profile>
> </hardware_profiles>
> <actions>
> <link href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/instances;image_id=9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' method='post' rel='create_instance' />
> </actions>
> </image>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DTACLOUD-181) json output from creating an image
(from a stopped instance) in RHEV-M does not return readable hardware
profiles
Posted by "Marios Andreou (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marios Andreou updated DTACLOUD-181:
------------------------------------
Attachment: 0001-Fixes-DTACLOUD_181-json-output-of-HardareProfile-wit.patch
attached patch should resolve issue
> json output from creating an image (from a stopped instance) in RHEV-M does not return readable hardware profiles
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-181
> URL: https://issues.apache.org/jira/browse/DTACLOUD-181
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud commit version: 59659586a6783bd4c851056813ed8369d08d4589 - clone: from https://git-wip-us.apache.org/repos/asf/deltacloud.git
> Fedora 16
> rhevm 3.X
> Reporter: Ronelle Landy
> Assignee: Marios Andreou
> Priority: Minor
> Attachments: 0001-Fixes-DTACLOUD_181-json-output-of-HardareProfile-wit.patch
>
>
> Found when verifying DTACLOUD-170:
> The json output from creating an image from a STOPPED instance in rhevm returns the hardware profiles as:
> #<Deltacloud::HardwareProfile:0x7fa438754db8>
> The XML output from the same operation returns the hardware profiles as:
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> The complete output in both json and xml are copied below. Logging this as a sepate issue to DTACLOUD-170 as it is far more minor.
> >> Output in json
> curl -X POST -F "name=rlandyImage" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=json"
> {"image":{"owner_id":"xxx","href":"http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/c4ddf46e-3abb-4bce-962e-2b55d4a01594","actions":[{"create_instance":{"method":"post","href":"/api/instances;image_id=c4ddf46e-3abb-4bce-962e-2b55d4a01594"}}],"architecture":"x86_64","state":"\n locked\n ","name":"rlandyImage","id":"c4ddf46e-3abb-4bce-962e-2b55d4a01594","description":"Image description","hardware_profiles":["#<Deltacloud::HardwareProfile:0x7fa438758288>","#<Deltacloud::HardwareProfile:0x7fa438754db8>"]}}[rlandy@localhost /]$
> [rlandy@localhost /]$
> >> Output in xml
> [rlandy@localhost /]$ curl -X POST -F "name=rlandyImageXml" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=xml"
> <?xml version='1.0' encoding='utf-8' ?>
> <image href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' id='9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f'>
> <name>rlandyImageXml</name>
> <owner_id>xxx</owner_id>
> <description>Image description</description>
> <architecture>x86_64</architecture>
> <state>locked</state>
> <hardware_profiles>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/DESKTOP' id='DESKTOP' rel='hardware_profile'></hardware_profile>
> </hardware_profiles>
> <actions>
> <link href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/instances;image_id=9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' method='post' rel='create_instance' />
> </actions>
> </image>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (DTACLOUD-181) json output from creating an image
(from a stopped instance) in RHEV-M does not return readable hardware
profiles
Posted by "Ronelle Landy (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ronelle Landy closed DTACLOUD-181.
----------------------------------
Closing this issue as fixed - see test comments added above.
> json output from creating an image (from a stopped instance) in RHEV-M does not return readable hardware profiles
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-181
> URL: https://issues.apache.org/jira/browse/DTACLOUD-181
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud commit version: 59659586a6783bd4c851056813ed8369d08d4589 - clone: from https://git-wip-us.apache.org/repos/asf/deltacloud.git
> Fedora 16
> rhevm 3.X
> Reporter: Ronelle Landy
> Assignee: Ronelle Landy
> Priority: Minor
> Attachments: 0001-Fixes-DTACLOUD_181-json-output-of-HardareProfile-wit.patch
>
>
> Found when verifying DTACLOUD-170:
> The json output from creating an image from a STOPPED instance in rhevm returns the hardware profiles as:
> #<Deltacloud::HardwareProfile:0x7fa438754db8>
> The XML output from the same operation returns the hardware profiles as:
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> The complete output in both json and xml are copied below. Logging this as a sepate issue to DTACLOUD-170 as it is far more minor.
> >> Output in json
> curl -X POST -F "name=rlandyImage" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=json"
> {"image":{"owner_id":"xxx","href":"http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/c4ddf46e-3abb-4bce-962e-2b55d4a01594","actions":[{"create_instance":{"method":"post","href":"/api/instances;image_id=c4ddf46e-3abb-4bce-962e-2b55d4a01594"}}],"architecture":"x86_64","state":"\n locked\n ","name":"rlandyImage","id":"c4ddf46e-3abb-4bce-962e-2b55d4a01594","description":"Image description","hardware_profiles":["#<Deltacloud::HardwareProfile:0x7fa438758288>","#<Deltacloud::HardwareProfile:0x7fa438754db8>"]}}[rlandy@localhost /]$
> [rlandy@localhost /]$
> >> Output in xml
> [rlandy@localhost /]$ curl -X POST -F "name=rlandyImageXml" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=xml"
> <?xml version='1.0' encoding='utf-8' ?>
> <image href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' id='9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f'>
> <name>rlandyImageXml</name>
> <owner_id>xxx</owner_id>
> <description>Image description</description>
> <architecture>x86_64</architecture>
> <state>locked</state>
> <hardware_profiles>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/DESKTOP' id='DESKTOP' rel='hardware_profile'></hardware_profile>
> </hardware_profiles>
> <actions>
> <link href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/instances;image_id=9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' method='post' rel='create_instance' />
> </actions>
> </image>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (DTACLOUD-181) json output from creating an image
(from a stopped instance) in RHEV-M does not return readable hardware
profiles
Posted by "Ronelle Landy (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ronelle Landy reassigned DTACLOUD-181:
--------------------------------------
Assignee: Marios Andreou (was: Ronelle Landy)
Assigning back to Marios for comment.
Please let me know if there is an error in the test steps listed. Otherwise, patch will need a review/rework. Thanks.
> json output from creating an image (from a stopped instance) in RHEV-M does not return readable hardware profiles
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-181
> URL: https://issues.apache.org/jira/browse/DTACLOUD-181
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud commit version: 59659586a6783bd4c851056813ed8369d08d4589 - clone: from https://git-wip-us.apache.org/repos/asf/deltacloud.git
> Fedora 16
> rhevm 3.X
> Reporter: Ronelle Landy
> Assignee: Marios Andreou
> Priority: Minor
> Attachments: 0001-Fixes-DTACLOUD_181-json-output-of-HardareProfile-wit.patch
>
>
> Found when verifying DTACLOUD-170:
> The json output from creating an image from a STOPPED instance in rhevm returns the hardware profiles as:
> #<Deltacloud::HardwareProfile:0x7fa438754db8>
> The XML output from the same operation returns the hardware profiles as:
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> The complete output in both json and xml are copied below. Logging this as a sepate issue to DTACLOUD-170 as it is far more minor.
> >> Output in json
> curl -X POST -F "name=rlandyImage" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=json"
> {"image":{"owner_id":"xxx","href":"http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/c4ddf46e-3abb-4bce-962e-2b55d4a01594","actions":[{"create_instance":{"method":"post","href":"/api/instances;image_id=c4ddf46e-3abb-4bce-962e-2b55d4a01594"}}],"architecture":"x86_64","state":"\n locked\n ","name":"rlandyImage","id":"c4ddf46e-3abb-4bce-962e-2b55d4a01594","description":"Image description","hardware_profiles":["#<Deltacloud::HardwareProfile:0x7fa438758288>","#<Deltacloud::HardwareProfile:0x7fa438754db8>"]}}[rlandy@localhost /]$
> [rlandy@localhost /]$
> >> Output in xml
> [rlandy@localhost /]$ curl -X POST -F "name=rlandyImageXml" -F "description=Image description" -F "instance_id=59f35d07-093c-46a5-814b-d0c6084ef8c9" --user "uname:password" "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=xml"
> <?xml version='1.0' encoding='utf-8' ?>
> <image href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images/9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' id='9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f'>
> <name>rlandyImageXml</name>
> <owner_id>xxx</owner_id>
> <description>Image description</description>
> <architecture>x86_64</architecture>
> <state>locked</state>
> <hardware_profiles>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/SERVER' id='SERVER' rel='hardware_profile'></hardware_profile>
> <hardware_profile href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/hardware_profiles/DESKTOP' id='DESKTOP' rel='hardware_profile'></hardware_profile>
> </hardware_profiles>
> <actions>
> <link href='http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/instances;image_id=9c8777bf-8d65-40e8-8bd4-e6ddf42f7b2f' method='post' rel='create_instance' />
> </actions>
> </image>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira