Nextcloud update 20.0.8 -> 20.0.9: Exception: Updates between multiple major versions and downgrades are unsupported

UCS - Univention Corporate Server
,
#1

Nachdem ich unsere Nextcloudinstanz von 20.0.8 auf 20.0.9 über das UI aktualisiert habe, bekomme die oben erwähnte (irgendwie sinnfreie) Fehlermeldung.

Leider geben die Logs dazu auch nicht viel her:

root@nextc-40486529:/# cat /var/log/nextcloud-upgrade_21_05_17.log
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Setting log level to debug
Exception: Updates between multiple major versions and downgrades are unsupported.
Update failed
Maintenance mode is kept active
Resetting log level

 18409 actions.upgrade                  21-05-17 12:01:08 [    INFO]: Saving data from old container (nextcloud=20.0.8-0)
...
 18409 actions.upgrade.container.5d58   21-05-17 12:01:10 [   DEBUG]: Calling docker exec -u root 5d58ead5915000923d9a5c5f3fe14f2fb900f6297ec2a060250b0101d88c1417 /usr/share/univention-docker-container-mode/store_data_custom --app nextcloud --app-version 20.0.8-0 --error-file /var/univention/tmp/tmpsFTCLM
...
 18409 docker                           21-05-17 12:02:37 [   DEBUG]: Removing image: docker.software-univention.de/nextcloud:20.0.8-0
...
18409 actions.upgrade.container.ec47   21-05-17 12:02:18 [ WARNING]: The upgrade log is written to /var/log/nextcloud-upgrade_21_05_17.log within the nextcloud container
...

Hat das schon mal jemand beobachtet und kann mir sagen, wie ich das behebe?

Besten Dank und viele Grüße

Fix/Repair/(Re-)Register Univention Apps
#2

you should only upgrade nextcloud through univention appcenter when available - not inside the nextcloud docker app image.

to turn off maintenance mode see:

rg
Christian

#3

I did. But to digging the problem, I’ll guess I’ve to look into the container, cause everything UCS appcenter.log provides is an (more or less - domain join failed) suxxessful update from 20.0.8 to 20.0.9.

Fun Fact: config.php said 'version' => '17.0.2.1',

BTW, Turing off maintenance mode didn’t solve the issue. Maybe even older updates failed?

Documention said the following upgrade path was done in march via appcenter:
NextCloud 14.0.6-1 → 14.0.8-0 → 15.0.8-0 → 16.0.6-0 → 17.0.2-0 → 18.0.4-0 → 18.0.7-0 → 19.0.4-0 → 20.0.8-0

Regarding to the value in the config.php something stucket between 17 and 18?
So, solution would be?
Downgrade to 18.0.4-0? - Is this possible?

#4

I did it two years ago as described here:

#5

Hmm, now Memberserver (where Nextcloud is running) reporting, that it isn’t installed while master server, where the update from 20.0.8 to 20.0.9 was initiated still reporting it as installed.

Also I found the following variable:
appliance/apps/nextcloud/version: 12.0.5-0
Maybe that’s the initial version we started with :wink:

@Univention_Staff are there any known issues in a multinode system when one server initiating an docker update on another one?

#6

As I described in my thread linked above, you will need to change this entry to the recent version, too.

#7

You described appcenter, not appliance … I’ll guess thats an orphan entry …

#8

Looks like there are some leftovers:

sudo docker images | grep nextcloud
docker.software-univention.de/nextcloud                       20.0.9-0            1e6e540ebbd7        6 weeks ago         1.11GB
docker.software-univention.de/nextcloud                       17.0.2-0            043861cab1ae        16 months ago       663MB
docker.software-univention.de/nextcloud                       14.0.6-0            581af9be14e0        2 years ago         600MB

Maybe I’ve just need to re-register the 17.0.2 (how?) and than rerun the upgrade process

Mastodon