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 11 Packages Projects Releases 10 Wiki Activity

SonarQube update fails going from 25.10.0.114319 to 25.11.0.114957 #1940

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

Originally created by @krestaino on GitHub (Nov 6, 2025).

✅ Have you read and understood the above guidelines?

yes

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

SonarQube

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

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.0.11/3bf5476b8a4699e2 (running kernel: 6.17.2-1-pve)

📝 Provide a clear and concise description of the issue.

The update script for SonarQube is failing during the update while executing the following command: curl -fsSL "https://binaries.sonarsource.com/Distribution/sonarqube/sonarqube-${RELEASE}.zip" -o $temp_file

Subsequent runs of update result in "No SonarQube Installation Found".

   _____                        ____        __       
  / ___/____  ____  ____ ______/ __ \__  __/ /_  ___ 
  \__ \/ __ \/ __ \/ __ `/ ___/ / / / / / / __ \/ _ \
 ___/ / /_/ / / / / /_/ / /  / /_/ / /_/ / /_/ /  __/
/____/\____/_/ /_/\__,_/_/   \___\_\__,_/_.___/\___/ 
                                                     

   ✖️   No SonarQube Installation Found!
root@sonarqube:~#

🔄 Steps to reproduce the issue.

Step 1: Open console for SonarQube container
Step 2: Run update

❌ Paste the full error output (if available).

   _____                        ____        __       
  / ___/____  ____  ____ ______/ __ \__  __/ /_  ___ 
  \__ \/ __ \/ __ \/ __ `/ ___/ / / / / / / __ \/ _ \
 ___/ / /_/ / / / / /_/ / /  / /_/ / /_/ / /_/ /  __/
/____/\____/_/ /_/\__,_/_/   \___\_\__,_/_.___/\___/ 
                                                     

  ✔️   Update available: sonarqube 25.10.0.114319 → 25.11.0.114957
  ✔️   Stopped Service
  ✔️   Backup created
  ⏳   Installing sonarqubecurl: option -o: requires parameter
curl: try 'curl --help' or 'curl --manual' for more information

[ERROR] in line 43: exit code 0: while executing command curl -fsSL "https://binaries.sonarsource.com/Distribution/sonarqube/sonarqube-${RELEASE}.zip" -o $temp_file

root@sonarqube:~#

🖼️ Additional context (optional).

No response

Originally created by @krestaino on GitHub (Nov 6, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? SonarQube ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.0.11/3bf5476b8a4699e2 (running kernel: 6.17.2-1-pve) ### 📝 Provide a clear and concise description of the issue. The `update` script for SonarQube is failing during the update while executing the following command: `curl -fsSL "https://binaries.sonarsource.com/Distribution/sonarqube/sonarqube-${RELEASE}.zip" -o $temp_file` Subsequent runs of `update` result in "No SonarQube Installation Found". ``` _____ ____ __ / ___/____ ____ ____ ______/ __ \__ __/ /_ ___ \__ \/ __ \/ __ \/ __ `/ ___/ / / / / / / __ \/ _ \ ___/ / /_/ / / / / /_/ / / / /_/ / /_/ / /_/ / __/ /____/\____/_/ /_/\__,_/_/ \___\_\__,_/_.___/\___/ ✖️ No SonarQube Installation Found! root@sonarqube:~# ``` ### 🔄 Steps to reproduce the issue. Step 1: Open console for SonarQube container Step 2: Run `update` ### ❌ Paste the full error output (if available). ``` _____ ____ __ / ___/____ ____ ____ ______/ __ \__ __/ /_ ___ \__ \/ __ \/ __ \/ __ `/ ___/ / / / / / / __ \/ _ \ ___/ / /_/ / / / / /_/ / / / /_/ / /_/ / /_/ / __/ /____/\____/_/ /_/\__,_/_/ \___\_\__,_/_.___/\___/ ✔️ Update available: sonarqube 25.10.0.114319 → 25.11.0.114957 ✔️ Stopped Service ✔️ Backup created ⏳ Installing sonarqubecurl: option -o: requires parameter curl: try 'curl --help' or 'curl --manual' for more information [ERROR] in line 43: exit code 0: while executing command curl -fsSL "https://binaries.sonarsource.com/Distribution/sonarqube/sonarqube-${RELEASE}.zip" -o $temp_file root@sonarqube:~# ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 03:00:11 +03:00
OVERLORD commented 2026-02-05 03:00:20 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 6, 2025):

edit ~/.sonarqube and change version to something

=> run update again

@MickLesk commented on GitHub (Nov 6, 2025): edit ~/.sonarqube and change version to something => run update again
OVERLORD commented 2026-02-05 03:00:34 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Nov 6, 2025):

no, the update script is broken.... i'll fix it later

@tremor021 commented on GitHub (Nov 6, 2025): no, the update script is broken.... i'll fix it later
OVERLORD commented 2026-02-05 03:00:49 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 6, 2025):

just missed tmpfolder

@MickLesk commented on GitHub (Nov 6, 2025): just missed tmpfolder
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#1940
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?