Skip to content
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

Wallabag removed while upgrading to 2.5.1~ynh2 #153

Closed
Gofannon opened this issue Aug 9, 2022 · 3 comments
Closed

Wallabag removed while upgrading to 2.5.1~ynh2 #153

Gofannon opened this issue Aug 9, 2022 · 3 comments

Comments

@Gofannon
Copy link
Contributor

Gofannon commented Aug 9, 2022

Describe the bug

  1. Cannot upgrade app to latest version (2.3.8~ynh4 => 2.5.1~ynh2)
  2. Package cannot restore the "pre-backup" wallabag2-pre-upgrade1.tar after the failed upgrade
    1. application is removed from server
    2. restore from backup is ok

Context

  • Hardware: dedicated computer : kimsufi box
  • YunoHost version: 11.0.9 (beta bulleyes)
  • I have access to my server: Through SSH | through the webadmin
  • Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: yes
    • If yes, please explain: upgrade to beta yunohost version since May and Wallabag is broken since
  • Using, or trying to install package version/branch: stable / master
  • If upgrading, current package version: 2.3.8~ynh4

Steps to reproduce

  • from the webadmin, upgrade wallabag to the latest version (same from CLI)

Expected behavior

  1. Application should be upgraded
  2. if fails, should be restore to working state as before upgrade

Logs

2022-08-09 21:42:22,235: WARNING - 762  This backup archive can not be restored because it comes from a too-old YunoHost version.
2022-08-09 21:42:22,391: DEBUG - + [[ -d /etc/yunohost/apps/wallabag2 ]]
2022-08-09 21:42:22,392: DEBUG - + ynh_die '--message=Uhoh ... Yunohost failed to restore the app to the way it was before the failed upgrade :|'
2022-08-09 21:42:22,483: WARNING - Uhoh ... Yunohost failed to restore the app to the way it was before the failed upgrade :|

https://paste.yunohost.org/edoqiliwew.bash

from the log file, it seems that I am affected by #129 and needs to use the #133 to fix the database. Am I correct?

@lapineige
Copy link
Member

I think I had this issue too, backup is not automatically restored, doing it afterwards works.

from the log file, it seems that I am affected by #129 and needs to use the #133 to fix the database. Am I correct?

You do :)

I think the best way to fix this is to execute these commands : wallabag/wallabag#5233 (comment)

I can provide assistance about how to do it (in summary : connect to your Wallabag MySQL database (password found in yunohost app settings), execute the command, run the upgrade).

@Gofannon
Copy link
Contributor Author

I think I had this issue too, backup is not automatically restored, doing it afterwards works.

I was afraid that other people migrating to bulleyes might get stuck with this but I was running the beta so I don't know... Time will tell with the release of YunoHost 11 :)

You do :)

I think the best way to fix this is to execute these commands : wallabag/wallabag#5233 (comment)

I can provide assistance about how to do it (in summary : connect to your Wallabag MySQL database (password found in yunohost app settings), execute the command, run the upgrade).

Well, I went the "lazy way" by using #133 as an intermediate step to fix the DB. It went smoothly

2.3.8~ynh4 (old)=> 2.4.3~ynh1 (fix db) => 2.5.1~ynh2 (current)

Thanks for all the people working of the package!

@lapineige , you can close this issue if you want, it was a false alert.

If someone has to do the same steps:

  1. fix the DB
    yunohost app upgrade wallabag2 -u https://github.com/nicofrand/wallabag2_ynh/tree/upgrade-database-scheme

  2. then upgrade the app with normal means from YunoHost to get the last version

@lapineige
Copy link
Member

I was afraid that other people migrating to bulleyes might get stuck with this but I was running the beta so I don't know... Time will tell with the release of YunoHost 11 :)

Then we should know pretty soon as it was done :D

If it restores well afterwards, that's not a so big deal.

Well, I went the "lazy way" by using #133 as an intermediate step to fix the DB. It went smoothly

Great, thank you for the feedback, this means it's working ! 🎉

you can close this issue if you want, it was a false alert.*

It was not, this is important to document too 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants