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

Upgrading peertube from 5.2.1~ynh1 to 6.0.3~ynh1 failed #427

Open
g1smo opened this issue Feb 13, 2024 · 4 comments
Open

Upgrading peertube from 5.2.1~ynh1 to 6.0.3~ynh1 failed #427

g1smo opened this issue Feb 13, 2024 · 4 comments

Comments

@g1smo
Copy link

g1smo commented Feb 13, 2024

Upgrading via the web interface on yunohost version 11.2.10 failed, the full log is:
https://paste.yunohost.org/raw/punecesewe

Tried both web UI and CLI.

Yunohost is running on a debian 11 container.

What might be problematic is that nodejs 18 is installed (because we need it in some other projects hosted on the server)?

The following warning stands out:
2024-02-13 03:28:18,432: WARNING - ./upgrade: line 16: admin: unbound variable

@g1smo g1smo changed the title Upgrading peertube from 5.2.1-ynh1 to 6.0.3-ynh1 failed Upgrading peertube from 5.2.1~ynh1 to 6.0.3~ynh1 failed Feb 13, 2024
@frju365
Copy link
Member

frju365 commented Feb 15, 2024

I've the same problem on Yunohost Cinema.

@AkselRocks
Copy link

Same problem here.

YunoHost 11.2.10.3 (stable)

@fflorent
Copy link
Contributor

Please, search in existing issues, you will find that it's an issue already reported and a solution is provided here:
#416 (comment)

@g1smo
Copy link
Author

g1smo commented Mar 19, 2024

I see, somehow I missed that issue.
The fix worked for me. Though I do suggest keeping an issue that users are likely to still encounter, open, for visibility. Until a fix is deployed, either in the upgrade script or documentation.

POST_INSTALL.md documentation states that the admin username is "root", whereas the upgrade script expects an "admin" user?

I guess the workaround could be posted under known (upgrade) issues in doc/PRE_UPGRADE.md or the missing admin user could be added in the upgrade script?

The latter solution would bring a better user experience, I can develop and test if it's sensible.

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

4 participants