[
https://issues.apache.org/jira/browse/JCLOUDS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13761935#comment-13761935
]
Everett Toews commented on JCLOUDS-273:
---------------------------------------
I'm trying to reproduce your issue but haven't been able to so far. I'm running
jclouds 1.6.2 against OpenStack Grizzly. I can see that when I call
ServerApi.get(), I get the response JSON.
{code}
{"server": blah blah blah "metadata": {}}
{code}
So it looks like Nova returns an empty metadata (as opposed to null) if there
is no metadata. This translates to an empty Map in jclouds.
Can you enable logging in jclouds so you can examine the responses being
returned by OpenStack?
Have a look at the SLF4J section of
http://jclouds.incubator.apache.org/documentation/reference/jclouds-logging/
> JClouds OpenStack Nova v2.0 Server domian doesn't follow OpenStack formal
> documentation
> ---------------------------------------------------------------------------------------
>
> Key: JCLOUDS-273
> URL: https://issues.apache.org/jira/browse/JCLOUDS-273
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Reporter: Maty Grosz
>
> Using class org.jclouds.openstack.nova.v2_0.domain.Server – look at the
> constructor “protected Server(… parameters)”:
> OpenStack formal documentation says that the metadata attribute is optional.
> The constructor above calls to(checkNotNull(metadata, "metadata")) – and
> fails.
> No need to check that in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
