starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-26 09:46:06 +03:00

[GH-ISSUE #10453] Sonarqube Update Broken #2259

New issue

Closed

opened 2026-02-26 12:51:49 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 12:51:49 +03:00

Owner

Originally created by @Karlito83 on GitHub (Dec 31, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10453

✅ 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.

github.com/community-scripts/ProxmoxVE@2d859aba23/ct/sonarqube.sh (L46) <- this line tries to move the new version to /opt/sonarqube. But at this line:
github.com/community-scripts/ProxmoxVE@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). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10453 ### ✅ 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_

kerem

2026-02-26 12:51:49 +03:00

closed this issue
added the
bug
label

kerem referenced this issue

2026-02-26 13:34:13 +03:00

[PR #2259] [CLOSED] [core] Fix incorrect JSON date_created fields #3648

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#2259

No description provided.

Rows
Columns