starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 13 Packages Projects Releases 10 Wiki Activity

PVE Post Install can't finish with some options selected #1114

New Issue
Closed
opened 2026-02-04 23:09:09 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-04 23:09:09 +03:00
Owner
Copy Link

Originally created by @Jesper-TJ on GitHub (Jun 18, 2025).

✅ Have you read and understood the above guidelines?

yes

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

PVE Post Install

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/post-pve-install.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📝 Provide a clear and concise description of the issue.

When running the scripts, if clicking "no" on option "Correct 'ceph package sources?", the script can't finish in the end. It get's stuck when trying to update Proxmox (and proxmox then times out after a while, making the terminal stay orange coloured and not upgrading the machine).
Then, if manually running "apt update", you get an error declaring that there's a problem with the ceph repo and thats probably whats stopping the scripts. If you then run "apt upgrade", it works fine and upgrades everything correctly. If you then run the scripts again from the beggining but choose "yes" to the "Correct 'ceph package sources?" option, the scripts finishes AND updates + upgrades the machine successfully (like it should do).

🔄 Steps to reproduce the issue.

Run the script as normal and choose "yes" to every option except for "Correct 'ceph package sources?" and "Add (Disabled) 'pvetest' repository?".

❌ Paste the full error output (if available).

The terminal just stays on "Updating Proxmox VE (Patiance)...". If you hit enter (or wait long enough), the script will dissapear and the terminal will be coloured orange for the rest of the session (the colour from the "updating" part of the script will stay).

🖼️ Additional context (optional).

No response

Originally created by @Jesper-TJ on GitHub (Jun 18, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? PVE Post Install ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/post-pve-install.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📝 Provide a clear and concise description of the issue. When running the scripts, if clicking "no" on option "Correct 'ceph package sources?", the script can't finish in the end. It get's stuck when trying to update Proxmox (and proxmox then times out after a while, making the terminal stay orange coloured and not upgrading the machine). Then, if manually running "apt update", you get an error declaring that there's a problem with the ceph repo and thats probably whats stopping the scripts. If you then run "apt upgrade", it works fine and upgrades everything correctly. If you then run the scripts again from the beggining but choose "yes" to the "Correct 'ceph package sources?" option, the scripts finishes AND updates + upgrades the machine successfully (like it should do). ### 🔄 Steps to reproduce the issue. Run the script as normal and choose "yes" to every option except for "Correct 'ceph package sources?" and "Add (Disabled) 'pvetest' repository?". ### ❌ Paste the full error output (if available). The terminal just stays on "Updating Proxmox VE (Patiance)...". If you hit enter (or wait long enough), the script will dissapear and the terminal will be coloured orange for the rest of the session (the colour from the "updating" part of the script will stay). ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 23:09:09 +03:00
OVERLORD commented 2026-02-04 23:09:22 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jun 18, 2025):

Works perfectly on my systems. Make a screencast, otherwise it's impossible to reproduce this. The script is executed hundreds of times a day, and I've never heard of this behavior.

@MickLesk commented on GitHub (Jun 18, 2025): Works perfectly on my systems. Make a screencast, otherwise it's impossible to reproduce this. The script is executed hundreds of times a day, and I've never heard of this behavior.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
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
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1114
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?