SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-05-16 21:22:07 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Upgrade scripts to work with PBS 4 #1647

New Issue
Closed
opened 2025-11-20 05:14:09 -05:00 by saavagebueno · 11 comments
saavagebueno commented 2025-11-20 05:14:09 -05:00
Owner
Copy Link

Originally created by @yodaphone on GitHub (Aug 6, 2025).

🌟 Briefly describe the feature

Add support for Post Install Script to work with PBS 4

📝 Detailed description

Add support for Post Install Script to work with PBS 4

💡 Why is this useful?

Proxmox Backup Server 4 also uses Debian 13 (trixie) and updating this script will be helpful to run the post install script that worked great with Ver 3

Originally created by @yodaphone on GitHub (Aug 6, 2025). ### 🌟 Briefly describe the feature Add support for Post Install Script to work with PBS 4 ### 📝 Detailed description Add support for Post Install Script to work with PBS 4 ### 💡 Why is this useful? Proxmox Backup Server 4 also uses Debian 13 (trixie) and updating this script will be helpful to run the post install script that worked great with Ver 3
saavagebueno added the enhancement label 2025-11-20 05:14:09 -05:00
saavagebueno commented 2025-11-20 05:14:10 -05:00
Author
Owner
Copy Link

@fkrauthan commented on GitHub (Aug 6, 2025):

Not sure if this should be a separate issue but it would be great if the update script for the PBS LXC container could also perform the PBS4 upgrade (not sure if that is something in scope of that script)

@fkrauthan commented on GitHub (Aug 6, 2025): Not sure if this should be a separate issue but it would be great if the update script for the PBS LXC container could also perform the PBS4 upgrade (not sure if that is something in scope of that script)
saavagebueno commented 2025-11-20 05:14:10 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 7, 2025):

Debian 13 itself is not yet available as a template, so support is not possible. Only the old script continues to work and must be upgraded manually.

Image
@MickLesk commented on GitHub (Aug 7, 2025): Debian 13 itself is not yet available as a template, so support is not possible. Only the old script continues to work and must be upgraded manually. <img width="438" height="214" alt="Image" src="https://github.com/user-attachments/assets/4f3664de-5e9f-48da-bf22-ce30e3755c9f" />
saavagebueno commented 2025-11-20 05:14:10 -05:00
Author
Owner
Copy Link

@flo-m commented on GitHub (Aug 8, 2025):

Not sure if this should be a separate issue but it would be great if the update script for the PBS LXC container could also perform the PBS4 upgrade (not sure if that is something in scope of that script)

that would be really great

@flo-m commented on GitHub (Aug 8, 2025): > Not sure if this should be a separate issue but it would be great if the update script for the PBS LXC container could also perform the PBS4 upgrade (not sure if that is something in scope of that script) that would be really great
saavagebueno commented 2025-11-20 05:14:11 -05:00
Author
Owner
Copy Link

@paolomainardi commented on GitHub (Sep 1, 2025):

Sorry, can the script pbs4-upgrade.sh implemented in #7214 be used on PBS LXC 3?

@paolomainardi commented on GitHub (Sep 1, 2025): Sorry, can the script `pbs4-upgrade.sh` implemented in #7214 be used on PBS LXC 3?
saavagebueno commented 2025-11-20 05:14:11 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 1, 2025):

Thats an upgrade only from 3 to 4?

@MickLesk commented on GitHub (Sep 1, 2025): Thats an upgrade only from 3 to 4?
saavagebueno commented 2025-11-20 05:14:11 -05:00
Author
Owner
Copy Link

@paolomainardi commented on GitHub (Sep 1, 2025):

@MickLesk, yes, it's a simple PBS LXC v3 based on Debian 12. I tried it and it worked, but I encountered an issue with apt keys that I resolved using wget https://enterprise.proxmox.com/debian/proxmox-archive-keyring-trixie.gpg -O /usr/share/keyrings/proxmox-archive-keyring.gpg.

@paolomainardi commented on GitHub (Sep 1, 2025): @MickLesk, yes, it's a simple PBS LXC v3 based on Debian 12. I tried it and it worked, but I encountered an issue with apt keys that I resolved using `wget https://enterprise.proxmox.com/debian/proxmox-archive-keyring-trixie.gpg -O /usr/share/keyrings/proxmox-archive-keyring.gpg`.
saavagebueno commented 2025-11-20 05:14:11 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 1, 2025):

why enterprise keyring? and whats the error? - create an discussion or an issue, not on old requests

@MickLesk commented on GitHub (Sep 1, 2025): why enterprise keyring? and whats the error? - create an discussion or an issue, not on old requests
saavagebueno commented 2025-11-20 05:14:11 -05:00
Author
Owner
Copy Link

@paolomainardi commented on GitHub (Sep 1, 2025):

why enterprise keyring? and whats the error? - create an discussion or an issue, not on old requests

Sorry, you are totally right.

Anyway the error was this one:

root@pbs:~# apt update
Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://security.debian.org/debian-security trixie-security InRelease
Hit:3 http://deb.debian.org/debian trixie-updates InRelease
Get:4 http://download.proxmox.com/debian/pbs trixie InRelease [2,785 B]
Err:4 http://download.proxmox.com/debian/pbs trixie InRelease
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A7BCD1420BFE778E
Reading package lists… Done
W: GPG error: http://download.proxmox.com/debian/pbs trixie InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A7BCD1420BFE778E
E: The repository ‘http://download.proxmox.com/debian/pbs trixie InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

(Sorry I cannot find now to properly format it as code from the GitHub app, as I am moving)

And the enterprise keyring fixed it.

Back to the original question, is the script intended to be used even in the LXC context?

Thanks!

@paolomainardi commented on GitHub (Sep 1, 2025): > why enterprise keyring? and whats the error? - create an discussion or an issue, not on old requests Sorry, you are totally right. Anyway the error was this one: root@pbs:~# apt update Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://security.debian.org/debian-security trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Get:4 http://download.proxmox.com/debian/pbs trixie InRelease [2,785 B] Err:4 http://download.proxmox.com/debian/pbs trixie InRelease The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A7BCD1420BFE778E Reading package lists… Done W: GPG error: http://download.proxmox.com/debian/pbs trixie InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A7BCD1420BFE778E E: The repository ‘http://download.proxmox.com/debian/pbs trixie InRelease’ is not signed. N: Updating from such a repository can’t be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. (Sorry I cannot find now to properly format it as code from the GitHub app, as I am moving) And the enterprise keyring fixed it. Back to the original question, is the script intended to be used even in the LXC context? Thanks!
saavagebueno commented 2025-11-20 05:14:11 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 1, 2025):

Yes

@MickLesk commented on GitHub (Sep 1, 2025): Yes
saavagebueno commented 2025-11-20 05:14:11 -05:00
Author
Owner
Copy Link

@paolomainardi commented on GitHub (Sep 1, 2025):

Ok thanks, I'll open an issue about the keyring problem.

@paolomainardi commented on GitHub (Sep 1, 2025): Ok thanks, I'll open an issue about the keyring problem.
saavagebueno commented 2025-11-20 05:14:12 -05:00
Author
Owner
Copy Link

@chrisjenx commented on GitHub (Sep 6, 2025):

Had this issue today, @paolomainardi workaround fixed it for me after I got the error

@chrisjenx commented on GitHub (Sep 6, 2025): Had this issue today, @paolomainardi workaround fixed it for me after I got the error
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1647
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?