-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
[Bug]: Update 24.0.0 beta2 to beta3, RC3 to final #31891
Comments
Can confirm same issue, finally restore from backup and avoid beta webpack.modules.js - can be deleted safely dist before (in ver 23) was located in ./core/js can confirm that problem exist if upgrade from 23 to 24b1 |
thanks for the report you need to delete these two files before running updater.phar again this is a known issue that will be ironed out for RC1 |
I've compared the files. the rc3 and final .tar.bz2 contains the latest updater.phar from git. On my personal instance (rc3) the updater.phar is different. This could mean that the updater was not replaced during the upgrade to RC3. |
This comment was marked as outdated.
This comment was marked as outdated.
@ChristophWurst did you double check your permissions on path/to/nc/updater[/updater.phar]? |
also, checked the updater.log? |
To avoid problems with migrations all the tables should be set to dynamic row format:
Had to add this to get the migrations up and running, before the mariadb server just die and restarted during the updates |
Finally converted all the tables with the script from here: |
|
Can confirm same issue 24b1 to 24final |
Beta1 was having the issue, the updater of beta 3 has (or latest rc1, but should be beta3) the fix. |
@ChristophWurst nothing striking in the log file… do you have another idea, why the updater was not replaced on your sys? on three other instances, mixed web and cli installer, i did not see the issue and the updaters were replaced correctly. |
I just tried an update with this results: Current version is 24.0.0 beta 1. Update to Nextcloud 24.0.0 available. (channel: "beta") Steps that will be executed: Start update? [y/N] y Info: Pressing Ctrl-C will finish the currently running step and then stops the updater. [✘] Check for expected files failed Update failed. To resume or retry just execute the updater again.
|
The instance was on |
that's ok, there was no dist folder on 23. The check kicks in before exchanging the files. |
23.0.0.10 to 24 RC3 was smooth. Only the RC3 to 24 final had the issue. The dist folder must have been the one of RC3. |
did GH lose my older comment? Here again: @schmidtvolker on Beta 1 this is expected and known. Delete the dist folder and continue with the upgrade as workaround. |
I would tell you if I knew. I checked the same things. I have no explanation, sorry. I have backups of the directory. Is there anything important info I could find in a time travel? |
@blizzz thx :) it works 👍 |
Could you e.g. dockerize and reprodce it? |
Same from 24.0.1 to 24.0.2 update. As a data point Workaround manual upgrade, which includes a new |
Another maybe more easy workaround would be to just replace the updater.phar file from a downloaded .tar of your Nextcloud version. Then you can update your Nextcloud instance with the new updater file. |
Sure it is easier, but I am not involved enough in the project to know, if there are any dependencies to the |
what are the permissions on the updater.phar for those affected? |
|
|
The web user does not have permissions to replace them. |
Yes, no clue where it came from, changed it to www-data and will keep an eye on it. |
Same from 24.0.2 to 24.03 update. |
My guess - problem exist if SELinux in enforcing mode |
Adding dist to the updater/index.php file solved the issue for me.
|
Confirmed for 24.0.4 to 24.0.5, thanks! |
Same problem out of the blue when upgrading from 24.0.5 to 24.0.7
|
I upgraded from 23.0.12 to 24.0.8 without issues and now trying to upgrade to 25.0.2 shows this error, I also manually changed updater/index.php |
Same issue when upgrading from 24.0.7 to 24.0.9 with |
This must have been a packaging issue for some 24.0.x releases. I fixed it by downloading that release, and replacing
|
Hi, please update to 25.0.7 or better 26.0.2 and report back if it fixes the issue. Thank you! My goal is to add a label like e.g. 26-feedback to this ticket of an up-to-date major Nextcloud version where the bug could be reproduced. However this is not going to work without your help. So thanks for all your effort! If you don't manage to reproduce the issue in time and the issue gets closed but you can reproduce the issue afterwards, feel free to create a new bug report with up-to-date information by following this link: https://github.com/nextcloud/server/issues/new?assignees=&labels=bug%2C0.+Needs+triage&template=BUG_REPORT.yml&title=%5BBug%5D%3A+ |
I just updated from 23.0.12 to 24.0.12. updater/index.php and updater/updater.phar were not updated and thus caused this error when subsequently attempting to update to 25.0.12. The checksums of the two files match the ones in https://github.com/nextcloud/updater/tree/v23.0.12 and have modification dates from Dec 17 2022 which is probably when I upgraded to 23.0.12. Fixed by manually overwriting the two files with the ones from nextcloud 24.0.12 similar to how rasos did it two comments above: #31891 (comment) After the upgrade to 25.0.12 I still have updater/index.php and updater/updater.phar matching 24.0.12. So I think the problem that updater files not being updated is still present in Nextcloud 25. If the issue remains after I get around to updating to Nextcloud 26 then I might make a new bug report. |
Bug description
[✘] Check for expected files failed
The following extra files have been found:
dist
webpack.modules.js
Update failed. To resume or retry just execute the updater again.
Steps to reproduce
Update from beta1 to beta2 was no problem
Expected behavior
I was expecting a successful update from 24.0.0 beta2 to 24.0.0. beta3.
Installation method
Manual installation
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.0
Web server
Apache (supported)
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
No response
Are you using the Nextcloud Server Encryption module?
Encryption is Enabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: