Open thegreenbear opened 2 months ago
Interestingly, it seems Nextcloud searches for an object called urn:oid:168
.
But this object does not exists on the S3 storage. At least not after the rollback (as in, restore previous container volumes and revert to image containing 29.0.2).
Hello there, Just to say I'm happy to help troubleshoot this issue if I can. I don't know much about NextCloud but I do have a dev env where I reproduced the issue. So I'm happy to test for whoever has ideas what to do :-D Cheers,
⚠️ This issue respects the following points: ⚠️
Bug description
Upgrading from Nextcloud 29.0.2.2 to 29.0.3.4 fails with the following message:
I am using the manual all-in-one deployment (it's been working great!) The containers tag used for version 29.0.2.2 was:
20240617_084300-latest
The containers tag used for version 29.0.3.4 was:20240701_074701-latest
My set up is a bit special as I am using S3 as primary storage and encryption.Note that I have 2 setups (one test, one prod) and both show the same behavior.
I have seen some issues on GitHub with the same error message but they seemed to apply to older versions of Nextcloud.
Steps to reproduce
Note: my two setups were initially deployed with 28.x.x. I'm not sure if the earlier upgrade path is relevant or not. If it helps, I'm happy to test this specific point.
Expected behavior
Upgrade should work. Nextcloud should start.
Nextcloud Server version
29
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
Updated from a MINOR version (ex. 28.0.1 to 28.0.2)
Are you using the Nextcloud Server Encryption module?
Encryption is Enabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Also these seem relevant:
Additional info
No response