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

Sonarqube Update Broken #2260

New Issue
Closed
opened 2026-02-05 04:21:00 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-05 04:21:00 +03:00
Owner
Copy Link

Originally created by @Karlito83 on GitHub (Dec 31, 2025).

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

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

Sonarqube CT

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

udpate

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📈 Which Proxmox version are you on?

9.1.4

📝 Provide a clear and concise description of the issue.

When calling "update" on an existing container, the script stops working. I don't remember the error shown on the first try, but the message below appeared when I called the script some days later, after I had the nerve to try again.

2d859aba23/ct/sonarqube.sh (L46) <- this line tries to move the new version to /opt/sonarqube. But at this line:
2d859aba23/ct/sonarqube.sh (L38) a folder named "/opt/sonarqube-backup" has been created so that the former line will fail.

Suggested fix:
mv /opt/sonarqube-* /opt/sonarqube -> mv "/opt/sonarqube-${RELEASE}" /opt/sonarqube

🔄 Steps to reproduce the issue.

call "update" when an update is available.

❌ Paste the full error output (if available).

✖️ No SonarQube Installation Found!

🖼️ Additional context (optional).

No response

Originally created by @Karlito83 on GitHub (Dec 31, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? Sonarqube CT ### 📂 What was the exact command used to execute the script? udpate ### ⚙️ What settings are you using? - [ ] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📈 Which Proxmox version are you on? 9.1.4 ### 📝 Provide a clear and concise description of the issue. When calling "update" on an existing container, the script stops working. I don't remember the error shown on the first try, but the message below appeared when I called the script some days later, after I had the nerve to try again. https://github.com/community-scripts/ProxmoxVE/blob/2d859aba23f1dab99540705bc448f23a67448f00/ct/sonarqube.sh#L46 <- this line tries to move the new version to /opt/sonarqube. But at this line: https://github.com/community-scripts/ProxmoxVE/blob/2d859aba23f1dab99540705bc448f23a67448f00/ct/sonarqube.sh#L38 a folder named "/opt/sonarqube-backup" has been created so that the former line will fail. Suggested fix: mv /opt/sonarqube-* /opt/sonarqube -> mv "/opt/sonarqube-${RELEASE}" /opt/sonarqube ### 🔄 Steps to reproduce the issue. call "update" when an update is available. ### ❌ Paste the full error output (if available). ✖️ No SonarQube Installation Found! ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 04:21:00 +03:00
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#2260
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?