Nextcloud update pushed too early?

[avatar1024]

Right so it's fixed on that broken. It turns out that for some reasons the ownership on many directories inside the NC data directory have been changed from www-data to yellowtent. This included the content of: data/appdata_{instanceid}/appstore/ which looked like:

drwxr-xr-x  3 yellowtent yellowtent 4.0K Oct  2 12:55 .
drwxr-xr-x 19 www-data   www-data   4.0K Oct  2 12:55 ..
-rw-r--r--  1 yellowtent yellowtent  87K Oct  1 11:19 appapi_apps.json
drwxr-xr-x  5 yellowtent yellowtent 4.0K Oct  1 11:19 app-discover-cache
-rw-r--r--  1 yellowtent yellowtent 2.8M Oct  1 11:19 apps.json
-rw-r--r--  1 yellowtent yellowtent 161K Oct  1 11:19 categories.json
-rw-r--r--  1 yellowtent yellowtent 7.2K Oct  1 11:19 discover.json

...and which broke the App Store. Revering the permission to www-data made everything work right away.

But actually many directories are affected inside the appdata_{instanceid} directory as well as users files inside the data directory.

I'm going to do a good backup and put the app in maintenance mode before I change ownership every inside the data because it feels a bit scary.

@staff Any clues on how it happened??

[avatar1024]

@staff quick question. When Nextcloud 32.0.1 gets released, will it be possible to update directly to it for those instance that are still on NC31, skipping 32.0.0?

[girish]

@avatar1024 good idea, we can revoke 32.0.0 so it can be skipped.

[avatar1024]

@girish on my instances NC still tries to first update to 32.0.0 despite 32.0.1 having now been pushed.

[nebulon]

@avatar1024 thanks for the reminder. Since the patch release package is out now, I've revoked the previous one. The update should now directly hop onto 32.0.1 (maybe check manually for updates first via the dashboard)

[ekevu123]

Upgrading to 32.0.1 worked well for me.

[avatar1024]

Yes the update now works directly from version 31.0.9 to 32.0.1. However, FYI, updating to 32.0.1 does not happen automatically and is still marked as a "pre-release and not considered stable yet". If this is intended just ignore me, but thought I'd let you know in case that was oversight (given that was not even the case when 32.0.0 got pushed).

[nebulon]

So the app is marked as stable from our side, I also don't think we even have the functionality to mark individual app versions as unstable. So not quite sure what you refer to. Do you have more info on that?

[avatar1024]

Here is what I see when I press the update button manually:

Auto-updates are enabled, yet the app does not auto-update. And this is the case on two different instances. In fact it also does not update automatically from 32.0.0 to 32.0.1.

[nebulon]

oh! yes I forgot about that aspect of update control. Thanks for letting us know. I have set it now to show a stable update for all. Sorry for the confusion.