-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Upgrade all apps after/during running the upgrader with occ #11102
Comments
GitMate.io thinks possibly related issues are #10918 (Occ Upgrade forces to run once a day), #6960 (occ upgrade is outdated), #10954 (OCC upgrade throws unhandled exception), #8092 (Upgrade notice should not be displayed when occ is run with --output=json), and #10949 ([WORKAROUND] NC14 RC2: occ upgrade hangs on running cronjob it states). |
Had the same issue too... |
Should be fixed with 14.0.1, pls test. |
Same here while upgrading from 14.0.0.19 to 14.0.1.1. Had to reactivate the apps manualy. Have to say that I used the updatescript from @enoch85...
https://github.com/nextcloud/vm/blob/master/nextcloud_update.sh |
@jospoortvliet Is a trigger needed like in NC 13 or is it done automatically? @JSoko The update script in the VM does a |
|
Same symptoms here. It seems that this behavior has changed since NC14. I'm wondering now if the documentation in step 8 is still valid and which of the following procedures is correct:
|
Before NC14 we used So adding back |
Nope, it's not fixed. This is 14.0.1 --> 14.0.3:
|
The thing that is fixed is that the app store had incompatible apps still. Only those get disabled, not compatible apps. Try to upgrade now, you should not have any app disable unless they actually ARE incompatible. And if they are you should see that before you upgrade in the upgrade screen. |
@jospoortvliet That doesn't explain why If the apps were incompatible then Example of apps that gets disabled:
Tried again today from 14.0.1 --> 14.0.3 still same behavior. |
https://www.youtube.com/watch?v=cPr8EPxWda0 Added with 14.0.1 -- 14.0.3. So this should be labeled bug instead? cc @MorrisJobke |
I see this everywhere... nextcloud/fulltextsearch#395 (comment)
So to update all apps they need to be disabled first? |
Usually not. Where was it written, that it needs to be like that? Is this the case if the old app is not compatible with 14 and the new app not compatible with 13? cc @nickvergessen @rullzer |
Could be. I'm not sure to be honest. |
Just ran into the the very same issue (I think). Updated my instance from 14.0.2 to 15 RC1. Got
In contrast to the apps that were still compatible, these were not updated. I had to update them manually and re-enable. |
Ref #8380 cc @nickvergessen |
I have this exact issue after upgrading to 16.0.0 with the web upgrader. Some critical app like calendar are not activated nor upgraded |
How can I force apps upgrade? |
@loxK In the Nextcloud VM we use occ: https://github.com/nextcloud/vm/blob/master/nextcloud_update.sh#L210 + this script to reinstall all the disabled apps again: https://github.com/nextcloud/vm/blob/master/static/recover_apps.py The recover script only works on the VM though, it's not default. |
Upgraded to NC 14 today and about 20 apps where deactivated due to that they where "incompatible". I then had to go to the App Store and manually re-enable them. In 13.0.6 I didn't have to as the option
--no--app-disable
could be used, and the apps where upgraded automatically. Why did you remove that?Please upgrade all apps before running the upgrade of all the rest when running with the
occ
command, or please add back the--no-app-disable
Thanks!
The text was updated successfully, but these errors were encountered: