OVH object storage - error when uploading

Seafile Server
31

That’s what we did, but as @haikuo said, the region is not working in the [block_backend] part.

32

Maybe several weeks I’m not sure, and what Jonathan said is right, after fixing this you can choose the region which contains your data.

33

Thanks for the feedback @haikuo!
I’ll wait for the fix :slight_smile:

I would also like to know if you are planning to support Keystone API v3?
I didn’t find any information on this in the forum.
For now, only the v2 is supported (changing v2.0 to v3.0 in seafile.conf throws an error).

However, the v2 is deprecated: https://developer.openstack.org/api-ref/identity/v2/
The v3 is the current version https://developer.openstack.org/api-ref/identity/v3/

This could lead to support to be removed for v2 API by cloud providers.
And then Seafile would stop working.

34

We don’t have the plan for now, but we will consider it in the future if necessary.

35

any workaround? i don’t see any issue in official repo, related to this problem

36

@slav0nic No workarounds as far as I know.
Two new versions were released recently (see https://manual.seafile.com/changelog/changelog-for-seafile-professional-server.html).
So hopefully, it will be fixed soon.

37

i know, still not fixed

38

Ít is not “not fixed”. It has simply not been implemented. It is unsupported (so far).

1 Like
39

is here any issue on github related to this ‘feature’?

40

@Jonathan @daniel.pan any updates on this? its getting annoying

41

migrate.sh result:
2018-01-20 14:01:18,381 Start to migrate [commits] object
2018-01-20 14:01:18,382 Start to migrate [fs] object
2018-01-20 14:01:18,383 Start to migrate [blocks] object
2018-01-20 14:01:18,392 [commits] Failed to check object b1c10e391a4b19300bb41a25fd0d06c405370632 existence from repo 46f13be5-68de-4ba7-a13f-f539bda1e390:
2018-01-20 14:01:18,392 Failed to execute task:
2018-01-20 14:01:18,392 [commits] Failed to check object ff911c55da328857441ad9ace1e2f5bfd039202a existence from repo 46f13be5-68de-4ba7-a13f-f539bda1e390:
2018-01-20 14:01:18,393 [fs] Failed to check object b88ab96740ef53249b9d21fb3fa28050842266ba existence from repo 46f13be5-68de-4ba7-a13f-f539bda1e390:
2018-01-20 14:01:18,393 Failed to execute task:
2018-01-20 14:01:18,393 Failed to execute task:
2018-01-20 14:01:18,393 [commits] Failed to check object 45fc4a3caad4a2af023b22e1411b7ee33831b68e existence from repo 7d2af5de-a6c8-461b-b143-33ec038221e0:
2018-01-20 14:01:18,393 [blocks] Failed to check object 8663a70ef30a5987b440a621483af2044bae1e0a existence from repo 46f13be5-68de-4ba7-a13f-f539bda1e390:
2018-01-20 14:01:18,393 Failed to execute task:
2018-01-20 14:01:18,393 Failed to execute task:
2018-01-20 14:01:18,394 [fs] Failed to check object ce82cd5d9cd4ff32c118bd91624711c83c3b61f6 existence from repo 46f13be5-68de-4ba7-a13f-f539bda1e390:
2018-01-20 14:01:18,394 Failed to execute task:
2018-01-20 14:01:18,394 [commits] Failed to check object a46a1ed264feac3bc6bd2814b7c11c91ea43a40c existence from repo 7d2af5de-a6c8-461b-b143-33ec038221e0:
2018-01-20 14:01:18,394 [blocks] Failed to check object 8663a70ef30a5987b440a621483af2044bae1e0a existence from repo 7d2af5de-a6c8-461b-b143-33ec038221e0:
2018-01-20 14:01:18,394 [fs] Failed to check object aa79ab9f7054c2665c0f4c4724d6d7e68184b521 existence from repo 7d2af5de-a6c8-461b-b143-33ec038221e0:
2018-01-20 14:01:18,394 Failed to execute task:
2018-01-20 14:01:18,394 Failed to execute task:
2018-01-20 14:01:18,394 [fs] Failed to check object b88ab96740ef53249b9d21fb3fa28050842266ba existence from repo 7d2af5de-a6c8-461b-b143-33ec038221e0:
2018-01-20 14:01:18,394 Failed to execute task:
2018-01-20 14:01:18,395 Failed to execute task:
2018-01-20 14:01:18,397 Complete migrate [blocks] object
2018-01-20 14:01:18,398 Complete migrate [commits] object
2018-01-20 14:01:18,398 Complete migrate [fs] object
Done.

42

The fix will be included in the next release 6.2.7.

3 Likes
43

Just tried the new version, but I still got the same error.

Here are the logs

[01/23/2018 05:34:51 AM] ../common/block-backend-swift.c(496): Put block 2768b64ca6fed624e9ece372921a380541ec9025 error 404. Response:
<html><h1>Not Found</h1><p>The resource could not be found.</p></html>
[01/23/2018 05:34:51 AM] ../common/fs-mgr.c(554): failed to commit chunk 2768b64ca6fed624e9ece372921a380541ec9025.
[01/23/2018 05:34:51 AM] repo-op.c(1100): failed to index blocks
44

May we assume you run your tests against the OVH storage backend when you claim this as fixed?

45

He meant next release. They had to release 6.2.7 to fix some small bug on 6.2.6, so the real fix will be in 6.2.8

1 Like
46

Hey there,

6.2.8 has been released ( https://manual.seafile.com/changelog/changelog-for-seafile-professional-server.html ) but I see no mention about this issue being fixed.
I upgraded and tried it and still got the same error.

Setting a variable to the right value is that complicated as 4 months is not enough to fix it?

47

As I already said, it will be included in next release (they had to release 6.2.8 to fix some issues on 6.2.7)

48

Ok, thanks @Cardiak !

49

works fine now. remember to use tenant name instead of tenant ID

50

Right :slight_smile: Thanks for the help !