SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Proxmox VE Post Install problems wehn upgrade from 8to9..... #1891

New Issue
Closed
opened 2025-11-20 05:19:22 -05:00 by saavagebueno · 6 comments
saavagebueno commented 2025-11-20 05:19:22 -05:00
Owner
Copy Link

Originally created by @4920441 on GitHub (Sep 12, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Proxmox VE Post Install

📂 What was the exact command used to execute the script?

apt update && apt dist-upgrade after changing the reps to trixie

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📈 Which Proxmox version are you on?

8.41

📝 Provide a clear and concise description of the issue.

White upgrading the nagscreen away script (which you shouldn't use anyway) fails and prevents apt from being successfull, which givies a wrong errorcode after/while upgrading.

🔄 Steps to reproduce the issue.

update ceph, update the rest to trixie -> Bam!

❌ Paste the full error output (if available).

🖼️ Additional context (optional).

No response

Originally created by @4920441 on GitHub (Sep 12, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Proxmox VE Post Install ### 📂 What was the exact command used to execute the script? apt update && apt dist-upgrade after changing the reps to trixie ### ⚙️ What settings are you using? - [ ] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📈 Which Proxmox version are you on? 8.41 ### 📝 Provide a clear and concise description of the issue. White upgrading the nagscreen away script (which you shouldn't use anyway) fails and prevents apt from being successfull, which givies a wrong errorcode after/while upgrading. ### 🔄 Steps to reproduce the issue. update ceph, update the rest to trixie -> Bam! ### ❌ Paste the full error output (if available). - ### 🖼️ Additional context (optional). _No response_
saavagebueno added the 🛑 Failure to comply with the guidelines label 2025-11-20 05:19:22 -05:00
saavagebueno commented 2025-11-20 05:19:22 -05:00
Author
Owner
Copy Link

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

More Info. What failed? Logs? Outputs? Nobody can Work with such Issues without any information

@MickLesk commented on GitHub (Sep 12, 2025): More Info. What failed? Logs? Outputs? Nobody can Work with such Issues without any information
saavagebueno commented 2025-11-20 05:19:23 -05:00
Author
Owner
Copy Link

@4920441 commented on GitHub (Sep 12, 2025):

Yes you can: because the script which removes the nag screen exits not cleanly and throws an error code when the file it should edit is not there any more (at one time in the upgrade process).

Therefore, apt exits unclean.

A Workaround would be to unapply the script, upgrade and apply the script again.

@4920441 commented on GitHub (Sep 12, 2025): Yes you can: because the script which removes the nag screen exits not cleanly and throws an error code when the file it should edit is not there any more (at one time in the upgrade process). Therefore, apt exits unclean. A Workaround would be to unapply the script, upgrade and apply the script again.
saavagebueno commented 2025-11-20 05:19:23 -05:00
Author
Owner
Copy Link

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

You can simply ignore my question completely and just answer something else.

@MickLesk commented on GitHub (Sep 12, 2025): You can simply ignore my question completely and just answer something else.
saavagebueno commented 2025-11-20 05:19:23 -05:00
Author
Owner
Copy Link

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

ive upgraded several systems and no issues. Without correct output, log, description, screenshots i close this

@MickLesk commented on GitHub (Sep 12, 2025): ive upgraded several systems and no issues. Without correct output, log, description, screenshots i close this
saavagebueno commented 2025-11-20 05:19:23 -05:00
Author
Owner
Copy Link

@4920441 commented on GitHub (Sep 12, 2025):

do what you want. I think my part on this.

@4920441 commented on GitHub (Sep 12, 2025): do what you want. I think my part on this.
saavagebueno commented 2025-11-20 05:19:23 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Sep 12, 2025):

I've upgraded also multiple hosts to v9.0 without issues with the script. Closing this because you failed to give relevant information asked.
We cant work blindly on this.

@tremor021 commented on GitHub (Sep 12, 2025): I've upgraded also multiple hosts to v9.0 without issues with the script. Closing this because you failed to give relevant information asked. We cant work blindly on this.
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 🛑 Failure to comply with the guidelines
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#1891
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?