New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Can't update to 28.0.0 since migration 28000Date20230906104802 fails #42173
Comments
As a workaround and since I had not used social a lot other than for testing, I disabled the social app - which didn't resolve the problem yet - so I also deleted all the related tables:
Now I can at least finalize the update and get back to my nextcloud instance. |
That migration doesn't have anything to do with the
Also, those table names for the https://github.com/nextcloud/social/blob/master/lib/Migration/Version1000Date20230217000002.php It also looks like the latest Social version (0.6.1) in the appstore was released back in June so I'm skeptical it's really NC28 ready. |
Also similar to #41253 reported earlier with the beta. And a similar report on the forum (which, in this case, was for these same tables): https://help.nextcloud.com/t/update-error-after-upgrading-from-nc-27-to-28beta/173532/3 |
Duplicate of #41253 Let's consolidate there. |
I have dropped all |
Bug description
After update to 28.0.0 and while running
occ upgrade
, we get this output:Steps to reproduce
occ upgrade
Expected behavior
The upgrade should succeed.
Installation method
Community Manual installation with Archive
Nextcloud Server version
28
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 22 to 23)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: