jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Gaul (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-1380) Multiple IT/Live test failures with Openstack Swift
Date Wed, 14 Feb 2018 16:06:00 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364334#comment-16364334
] 

Andrew Gaul commented on JCLOUDS-1380:
--------------------------------------

[~cstamas], Ceph is a Swift clone and may not support all the features that we test.  For
example, I test against Rackspace CloudFiles, an OpenStack Swift deployment, and see:

{noformat}
Failed tests:
  CloudFilesUSStaticLargeObjectApiLiveTest>StaticLargeObjectApiLiveTest.testDelete:71->StaticLargeObjectApiLiveTest.assertDelete:145
expected [0] but found [1]

Tests run: 140, Failures: 1, Errors: 0, Skipped: 12
{noformat}

Some of these failures are likely Ceph bugs, like lack of Cache-Control, lack of SLO delete,
and lack of bulk extract archive support, while others seem configuration-specific like quota
errors.  These failures do not mean that jclouds has problems or is not useful when connecting
to Ceph, rather that if you use certain features then they won't work with Ceph due to issues
with its implementation.

I wonder why you use the Ceph Swift API instead of S3?  The latter is likely better supported.

> Multiple IT/Live test failures with Openstack Swift
> ---------------------------------------------------
>
>                 Key: JCLOUDS-1380
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1380
>             Project: jclouds
>          Issue Type: Test
>            Reporter: Cservenak, Tamas
>            Priority: Major
>         Attachments: openstack-swift-2.0.x.txt
>
>
> I have access to Openstack Swift instance and am planning to use JClouds to access it.
Hence, just "for fun" I tried the IT/Live test suite against swift instance, and got several
test failures.
> {{Tests run: 165, Failures: 36, Errors: 0, Skipped: 35}}
> Built the *master* branch of jclouds (88c84af8788116be2b1f492c3314e07b493dc6f2).
> How can I contribute to swift api improvements? Should I share the surefire-reports folder
with failure details (is it enough? would it contain some sensitive data, ie. swift credentials/URLs
I used?)
> Since am toying with 2.0.3 version, am planning to try the 2.0.x branch too.
> TIA



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message