Open dee-kryvenko opened 9 months ago
Looks like maybe nextcloud/text#4823 (fixed by nextcloud/text#4824) and/or nextcloud/text#3404 (fixed by nextcloud/text#4286). The former should have been released with NC V27.1.4 (it was backported in nextcloud/text#4968), but I see no version bump in the shipped Text app (from v3.8.0) in a stock NC v27.1.4 installation so maybe something got messed up there. I don't think nextcloud/text#4286 was backported, but it should be IMO.
So, in any case, this may be a Text app only issue, but until confirmed I'll leave here in this repo (plus it's a shipped app so we definitely want it to work well!)
Cc: @max-nextcloud @juliushaertl
Hmmm it didn't occur to me that the issue may be with UI not with S3 storage. Indeed both local and S3 versions are getting messed up in the end. Let me test this with a) md files on local disk and b) files other than md files.
Ok yes, I can definitely reproduce the same with SMB external storage as well. https://github.com/nextcloud/text/issues/3404 gave me the key - it is increasingly likely to reproduce if I keep making changes and saves without exiting text editor.
Doesn't look like I can reproduce it on S3 external storage by uploading new versions of files via UI, or editing it on my machine mounted as webdav. Good news I don't have to worry about integrity of my non-text files. Bad news, my KB might be corrupted as much as in my own head lol
⚠️ This issue respects the following points: ⚠️
Bug description
I am observing data in my S3 bucket (AWS) inconsistent with content on my Nextcloud server. See repro steps for more details, I did came across this issue https://github.com/nextcloud/server/issues/41917 which may or may not be related, my symptoms are slightly different and this is not a new issue - I observed it for two months, I was waiting for https://github.com/nextcloud/fulltextsearch_elasticsearch/issues/326 to be fixed before reporting this on the off chance it was related.
Steps to reproduce
test.md
via NextCloud UI, click save, exit the editor.Initial version
andCurrent version
, both0 B
.Standard
storage class and second (current) will beIntelligent-Tiering
- not sure if this is AWS or NextCloud doing, I would expect them both beIntelligent-Tiering
since my bucket is configured for it. This is a first sign of trouble, that there are two versions from get-go and that one version is a wrong storage class.test.md
in UI, addfirst line
content, save the file, exit the editor.Details
->Version
that there is now a third versionCurrent version
correctly opening. The first two empty versions do not open, they are presenting a loading spinner forever and nothing pops up in the logs.test.md
in UI, addsecond line
content, save the file, exit the editor.Details
->Version
that there is now a new version, with correct new content.test.md
in UI, addthird line
content, save the file, exit the editor.Details
->Version
that there is now a new version, with correct new content.Additional details
I did not notice causality between how fast I am making changes and inconsistencies, it may occur on singular isolated edits. Although I did notice correlation, it is occurring more often on fast edits, which is a typical use case for a Markdown KB (add a thought, save, edit, save etc - and you never know if your latest edit actually made it to S3).
You may notice under disabled apps I have
files_versions_s3
- I tried to install it to see if it makes any difference, it didn't. It was having this behavior before I ever installed it.Expected behavior
Expected to see clear linear version history both in NextCloud and S3, and most importantly - expecting to always see latest and consistent content on S3. In my home use scenario, S3 should be the most reliable storage for most important documents and KB, because my home lab hardware may always be stolen or destroyed, and traditional scheduled backups are never latest. This bug is preventing me from fully trusting NextCloud over Google Drive. I may never be sure that my off-site data is consistent.
Installation method
Official All-in-One appliance
Nextcloud Server version
27
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
Web server
Other
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
Fresh Nextcloud Server install
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
No response
Additional info
No response