-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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]: Upgrade FAILED: ERROR: column "type" does not exist at character 45 #46879
Comments
Did you check crazy-max/docker-nextcloud#170 (comment) ? You should always upgrade to the latest minor before attempting to upgrade to the next major. |
cc @provokateurin @tobiasKaminsky there was something weird with the migration? |
Well that comment is to my problem I reported - so no, I did not know that.. Wouldn't it make sense to implement a check for this if such attempt of skipping minor version can entirely break the nextcloud instance? |
There is a check: The updater does not allow such an update. Other docker deployments often just replace the files, so there is no way for us to check. So should be part of that deployment. |
But I am still facing this error - How am I supposed to troubleshoot it now? What went wrong and how to fix it please. Thanks |
Sorry, that went badly. The migration https://github.com/nextcloud/server/pull/42820/files was not executed on your instance because it was just added with 28.0.2 and therefore the lazy and type columns are missing in the appconfig table. To make it even more confusing, we also changed the column definitions in a later migration step:
|
Well you should not allow the upgrade then and display error Upgrade not possible due to skipping some important versions.. I already migrated all my stuff to the new instance, but for the next time such safety check can save the whole weekend for someone in the future.. Thanks! |
The code update is deployed by the Docker image you're using. The second phase (the upgrade piece) is only triggered after the new version has already been deployed by the image. So the image's entrypoint needs to check for this. We cannot do so as already stated: #46879 (comment) |
Bug description
After performing upgrade (from
28.0.1
to29.0.3
) started having this problem - Nextcloud will end up in maintenance mode.Steps to reproduce
crazymax/nextcloud:latest
withpostgres:12
images28.0.1
Expected behavior
Successful upgrade and working nextcloud server instance
Installation method
Other Community project: crazymax/nextcloud
Nextcloud Server version
28.0.1
Operating system
Debian:12
PHP engine version
None
Web server
None
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 28 to 29)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: