Repository navigation
Failed migration of a disabled app blocks the instance after a successful core upgrade, and all disabled apps stay off #9013
Steps to reproduce
Expected behaviour
Actual behaviour
Suggestions
Versions
Logs(the last block repeated on every restart, 240 times) |
Replies: 3 comments
|
Hi,
I agree. Please report this to https://github.com/nextcloud/server/issues if not already done.
Container updates and nc updates are already opt-out. There is a checkbox offered for daily backups that allows to configure this. |
|
Since I run into the same issue: @szaimen
|
|
Thanks. Looking further, the server side turns out to be covered already: nextcloud/server#66167 describes exactly this. On PHP 8.4 the post-upgrade schema check builds the migrations of disabled apps as lazy objects; that fails for a disabled app, and logging the failure then crashes @KaeTuuN: so no new server issue from my side; #66167 is the place for your information. What remains for AIO is the second half: before the update About the opt-out: understood. Our point was mainly that a major upgrade comes with the same checkbox as minor updates; separate checkboxes for minor and major updates, as suggested above, would cover that. |
Hi,
I agree. Please report this to https://github.com/nextcloud/server/issues if not already done.
Container updates and nc updates are already opt-out. There is a checkbox offered for daily backups that allows to configure this.