Repository navigation
Update to minor version drives to update to major version #18485
Description
Activity
- added0. Needs triagePending check for reproducibility or if it fits our roadmapPending check for reproducibility or if it fits our roadmap
on Dec 19, 2019 - There is a file
updater.logsomewhere. Please grab "[info] updateURL: xxxx" and post it here. - Modify nextcloud to log the updaterURL used by updatenotification app. Wait around 30 minutes (because the updater response is cached for 30 minutes) and visit the admin page again. Look for updateURL in nextcloud.log and post it here.
Index: lib/private/Updater/VersionCheck.php IDEA additional info: Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP <+>UTF-8 =================================================================== --- lib/private/Updater/VersionCheck.php (revision 29f6f15cf3c63df07b81d7c97fe547f27a3906b3) +++ lib/private/Updater/VersionCheck.php (date 1576767974554) @@ -87,6 +87,7 @@ //fetch xml data from updater $url = $updaterUrl . '?version=' . $versionString; + \OC::$server->getLogger()->info('updateURL: ' . $url); $tmp = []; try {The updater server should return the same update for the same request hence we need to figure out why the updater sends a different request then admin view. Thanks in advance 👍
- There is a file
Having the same issue when invoking the update via command line. It says update to 16.0.7 when checking the web gui and 17.0.2 with updater.phar.
As requested (hope it helps):
[info] updateURL: https://updates.nextcloud.com/updater_server/?version=16x0x6x1xxxstablexx2019-11-07T22%3A22%3A16%2B00%3A00+0e57eabfa0d510bcab79bc361f87d4b06f6deb85x7x3x11After applying your patch and waiting for an hour, the behavior is the same (gui proposes 16.0.7 and cli wants to install 17.0.2).
Thanks @Nils160988
Please check the nextcloud.log for updateURL.
You mean updater.log probably?
updateURL in updater.log stays the same and there is no entry in nextcloud.logNo.
nextcloud.log. The patch above should log the used updaterURL. Please ensure that your logging info message. Should be loglevel = 1. Updater itself is a component independent from nextcloud. Nextcloud and Updater both check the updater_server for available updates. I suspect that the request differs.Ah, was missing loglevel = 1...
nextcloud.log:
https:\/\/updates.nextcloud.com\/updater_server\/?version=16x0x6x1x1438463944.1522x1576840340xstablexxHmm. Could you recheck? The url is missing some parts (after stablexx should be something about your php version. 7x4x0 for example).
After stablexx there is some timestamp I thought is not part of the URL anymore...
This should be the full entry:
updateURL: https:\/\/updates.nextcloud.com\/updater_server\/?version=16x0x6x1x1438463944.1522x1576840340xstablexx2019-11-07T22:22:16+00:00 0e57eabfa0d510bcab79bc361f87d4b06f6deb85x7x3x11https://updates.nextcloud.com/updater_server/?version=16x0x6x1xxxstablexx2019-11-07T22%3A22%3A16%2B00%3A00+0e57eabfa0d510bcab79bc361f87d4b06f6deb85x7x3x11https://updates.nextcloud.com/updater_server/?version=16x0x6x1x1438463944.1522x1576840340xstablexx2019-11-07T22%3A22%3A16%2B00%3A00+0e57eabfa0d510bcab79bc361f87d4b06f6deb85x7x3x11Updater does not send the installation date. But the "chance" is derived from the installation date. "change" is the probability that nextcloud 16.0.7 or nextcloud 17.0.2 is announced to your instance. Without installation date the updater_server will announce you the first element (usually the newest one).
Never the less we should query the updater_server with the same data.
installedatandlastupdatedatare app values (=> they are stored in the database) hence not available to updater (onlyconfig.phpvalues are available). It's like that since a while and there are some other reports about this issue around. Not sure if it's a issue for many people.cc @nextcloud/server-triage for opinions
No, 16.0.6 should always get 16.0.7 offered
If so the updater_server has to be configured properly: https://github.com/nextcloud/updater_server/blob/4d34da73a480d6a9f5aac95e21b95053e954d1b9/config/config.php#L355-L384
I asked @jospoortvliet about that at some topic over at help.nextcloud.com and he told me that he will discuss this with the release managers.
But still the updater and updatenotification app are sending different requests.
- ghost addedstaleTicket or PR with no recent activityTicket or PR with no recent activity
on Jan 19, 2020 - ghost removedstaleTicket or PR with no recent activityTicket or PR with no recent activity
on Jan 19, 2020 This is getting a bit critical now regarding 17.0.5 and 18.0.3 security updates.
If I read the discussion #20119 correctly there is a security relevant bug in Nextcloud and the updates are kind of urgent.I have a 17.0.4 (stable) production system I do not want (and due to missing app support) cannot update to 18.0.3, but the updater is only offering 18.0.3.
So I have to choose between staying on 17.0.4 with a possibly security related flaw or update to 18.0.3 and loose apps.Not a pleasant decision...
Reacted by tuxmaster5000 and much-dogeUpdating manual is just fine in the meantime:
https://docs.nextcloud.com/server/latest/admin_manual/maintenance/manual_upgrade.html@nickvergessen Thank you for the quick reply, but I cannot stop or restart the webserver on shared hosting.
Or maybe it is sufficient to remove the subdomain connected to the webspace temporarily?Or maybe it is sufficient to remove the subdomain connected to the webspace temporarily?
yes, it's just to prevent people accessing it
Reacted by bpcurseIf so the updater_server has to be configured properly: https://github.com/nextcloud/updater_server/blob/4d34da73a480d6a9f5aac95e21b95053e954d1b9/config/config.php#L355-L384
I asked @jospoortvliet about that at some topic over at help.nextcloud.com and he told me that he will discuss this with the release managers.
But still the updater and updatenotification app are sending different requests.
@kesselb and @jospoortvliet so is there any update on this in the meantime? Given the MySQL 5.7 incompatibility issue with NC21, the update process should protect users from upgrading into an unsupported configuration. I expect the current behavior to create a lot of frustration and (hopeless) backup restoration activities for those people who assume to safely upgrade to the lastest NC20 version, while the system upgrades into an unusable state.
nextcloud-releases/updater_server#558 fixed the wrong updater_server configuration. 20.0.9 is now announced to every instance on 20.0.x.
Reacted by Georgiy Sitnikov
Steps to reproduce
Use Version e.g. .16.0.6, see that there is already newer 16.0.7 and other Major version 17.0.2 on the market.
See that Minor version presented and try to update to it (channel is Stable).

Try to do update and see that it is Major version instead:

Go back because I need minor update.
Expected behaviour
What is shown is what you get - if Update to 16.0.7 shown, it should be also in the updater, not new Major version.
Actual behaviour
Trying update to minor version drives to update to major version.
Server configuration
Operating system: Ubuntu 18.04
Web server: Apache/2.4.41 (Ubuntu)
Database: mysql Ver 15.1 Distrib 10.1.43-MariaDB, for debian-linux-gnueabihf (armv7l) using readline 5.2
PHP version: PHP 7.3.11
Nextcloud version: 16.06
Updated from an older Nextcloud/ownCloud or fresh install: Updated
Where did you install Nextcloud from: Official
Signing status:
Signing status
List of activated apps:
App list
Nextcloud configuration:
Config report
Are you using external storage, if yes which one: local + WebDAV
Are you using encryption: no
Are you using an external user-backend, if yes which one: No