OVH object storage - error when uploading


#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.


#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


#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 !