jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Daggett (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCLOUDS-580) updateMetadata on a Rackspace server fails with 400 badRequest
Date Mon, 02 Jun 2014 22:13:01 GMT

     [ https://issues.apache.org/jira/browse/JCLOUDS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jeremy Daggett updated JCLOUDS-580:
-----------------------------------

    Summary: updateMetadata on a Rackspace server fails with 400 badRequest  (was: updateMetada
on a Rackspace server fails with 400 badRequest)

> updateMetadata on a Rackspace server fails with 400 badRequest
> --------------------------------------------------------------
>
>                 Key: JCLOUDS-580
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-580
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 1.7.2
>            Reporter: Hugo Duncan
>
> When using an `updateMetadata` call on the Server API for Rackspace US passing a single
key and value, the result is a `400 badRequest` error.
> The annotation on ServerAsyncApi for this overload of `updateMetadata` seems difficult
to reconcile with the annotations on the overload passing a map for the tag data, and with
the API docs (http://docs.openstack.org/api/openstack-compute/2/content/Update_Metadata-d1e5208.html)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message