[
https://issues.apache.org/jira/browse/DTACLOUD-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ronelle Landy closed DTACLOUD-108.
----------------------------------
Resolution: Fixed
Closing this JIRA issue as per the fix from
https://bugzilla.redhat.com/show_bug.cgi?id=765855. The test comments are
copied below:
--------------------------
If RHEVM does not have 'floppyinject' capability, the following error is
returned (API output copied below):
curl -X POST -F "image_id=14ba9684-41c5-4917-858c-13303bf710bd" -F
"user_data=1|https://xxx|xxx_key|xxxxxxxx" --user 'username:password'
"http://server:3001/api/instances?format=xml";
<error status='500' url='/api/instances?format=xml'>
<kind>backend_error</kind>
<backend driver='rhevm'>
<code>500</code>
</backend>
<message><![CDATA[Unhandled exception or status code (Required VDSM hook
'floppyinject' not supported by RHEV-M)]]></message>
</error>
When the 'floppyinject' capability is added to that same RHEVM server:
curl -X POST -F "image_id=14ba9684-41c5-4917-858c-13303bf710bd" -F
"user_data=1|https://xxxx|xxxx_key|xxxxxxxxx" --user 'username:password'
"http://server:3001/api/instances?format=xml";
<?xml version='1.0' encoding='utf-8' ?>
<instance
href='http://server:3001/api/instances/e3ed6fab-52c8-4a3e-95f3-05c381d84b49'
id='e3ed6fab-52c8-4a3e-95f3-05c381d84b49'>
<name>xxx</name>
<owner_id>xxx</owner_id>
<image
href='http://server:3001/api/images/14ba9684-41c5-4917-858c-13303bf710bd'
id='14ba9684-41c5-4917-858c-13303bf710bd'></image>
<realm
href='http://server:3001/api/realms/ba2b3a52-4303-11e1-b6c2-5cf3fc1c861c'
id='ba2b3a52-4303-11e1-b6c2-5cf3fc1c861c'></realm>
<state>PENDING</state>
<hardware_profile href='http://server:3001/api/hardware_profiles/DESKTOP'
id='DESKTOP'>
<property kind='fixed' name='storage' unit='GB' value='1'></property>
<property kind='fixed' name='cpu' unit='count' value='1'></property>
<property kind='fixed' name='memory' unit='MB' value='512'></property>
</hardware_profile>
<actions>
<link
href='http://server:3001/api/images;instance_id=e3ed6fab-52c8-4a3e-95f3-05c381d84b49'
method='post' rel='create_image' />
</actions>
<launch_time>2012-01-20T14:17:17.038-05:00</launch_time>
<public_addresses><address port='xxxx'
type='vnc'>127.0.0.1</address></public_addresses>
<private_addresses></private_addresses>
</instance>
> RHEV-M user_data trouble
> ------------------------
>
> Key: DTACLOUD-108
> URL: https://issues.apache.org/jira/browse/DTACLOUD-108
> Project: DeltaCloud
> Issue Type: Bug
> Reporter: David Lutterkort
> Assignee: Michal Fojtik
>
> For a number of reasons, the current way how we do user_data injection in
> RHEV-M causes heartburn. To address that, we need to
> (a) take an antacid
> (b) only report feature :instances, :user_data if the capabilities for that
> RHEV-M provider contain "//custom_property[@name='floppyinject']" (ideally,
> cache this in a long-lived cache keyed by RHEV-M provider URL)
> (c) in rhevm_client.rb(create_vm) do not do any checks for version; instead,
> check if provider has floppyinject hook installed
> (d) take another antacid
--
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
