starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-16 05:34:07 +03:00
Code Issues 23 Packages Projects Releases 44 Wiki Activity

Incompatible upgrade of Omada Controller MongoDB #2148

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

Originally created by @JXF9527 on GitHub (Dec 11, 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?

Omada Controller

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/omada.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

9.0.11

📝 Provide a clear and concise description of the issue.

MongoDB does not support cross-version upgrades. If a lower version of MongoDB was previously installed, running this script will cause MongoDB to upgrade (even if I don't want to upgrade it). It is necessary to add verification and confirmation when upgrading MongoDB (prompting about cross-version data incompatibility, or simply not upgrading MongoDB at all).

🔄 Steps to reproduce the issue.

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/omada.sh)"

❌ Paste the full error output (if available).

Oct 20 11:28:28 omada systemd[1]: Starting tpeap.service - LSB: Omada Controller...
Oct 20 11:28:29 omada tpeap[128]: check omada
Oct 20 11:28:29 omada tpeap[128]: Starting Omada Controller. Please wait.
Oct 20 11:28:35 omada tpeap[128]: ......
Oct 20 11:28:35 omada tpeap[128]: Fail to start mongo DB server

🖼️ Additional context (optional).

No response

Originally created by @JXF9527 on GitHub (Dec 11, 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? Omada Controller ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/omada.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 9.0.11 ### 📝 Provide a clear and concise description of the issue. MongoDB does not support cross-version upgrades. If a lower version of MongoDB was previously installed, running this script will cause MongoDB to upgrade (even if I don't want to upgrade it). It is necessary to add verification and confirmation when upgrading MongoDB (prompting about cross-version data incompatibility, or simply not upgrading MongoDB at all). ### 🔄 Steps to reproduce the issue. bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/omada.sh)" ### ❌ Paste the full error output (if available). Oct 20 11:28:28 omada systemd[1]: Starting tpeap.service - LSB: Omada Controller... Oct 20 11:28:29 omada tpeap[128]: check omada Oct 20 11:28:29 omada tpeap[128]: Starting Omada Controller. Please wait. Oct 20 11:28:35 omada tpeap[128]: ...... Oct 20 11:28:35 omada tpeap[128]: Fail to start mongo DB server ### 🖼️ Additional context (optional). _No response_
OVERLORD added the not a script issue label 2026-02-05 03:57:11 +03:00
OVERLORD commented 2026-02-05 03:57:20 +03:00
Author
Owner
Copy Link

@JXF9527 commented on GitHub (Dec 11, 2025):

Perhaps we can handle it like unifi.sh does: do not process MongoDB during upgrades, and only install MongoDB in install.sh.

@JXF9527 commented on GitHub (Dec 11, 2025): Perhaps we can handle it like unifi.sh does: do not process MongoDB during upgrades, and only install MongoDB in install.sh.
OVERLORD commented 2026-02-05 03:57:26 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 11, 2025):

It is the Case?

@MickLesk commented on GitHub (Dec 11, 2025): It is the Case?
OVERLORD commented 2026-02-05 03:57:34 +03:00
Author
Owner
Copy Link

@JXF9527 commented on GitHub (Dec 11, 2025):

@MickLesk Yes, if upgrading from 4.4 to 7.0, you must upgrade incrementally: 4.4 -> 5.0 -> 6.0 -> 7.0

@JXF9527 commented on GitHub (Dec 11, 2025): @MickLesk Yes, if upgrading from 4.4 to 7.0, you must upgrade incrementally: 4.4 -> 5.0 -> 6.0 -> 7.0
OVERLORD commented 2026-02-05 03:57:41 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 11, 2025):

Show me the upgrade of mongo in the Script?

@MickLesk commented on GitHub (Dec 11, 2025): Show me the upgrade of mongo in the Script?
OVERLORD commented 2026-02-05 03:57:45 +03:00
Author
Owner
Copy Link

@JXF9527 commented on GitHub (Dec 11, 2025):

@MickLesk Perhaps the MongoDB upgrade process can be removed from the upgrade method.

@JXF9527 commented on GitHub (Dec 11, 2025): @MickLesk Perhaps the MongoDB upgrade process can be removed from the upgrade method.
OVERLORD commented 2026-02-05 03:57:51 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 11, 2025):

Then show me the Upgrade of Mongo in the update_script, then we can remove it.

@MickLesk commented on GitHub (Dec 11, 2025): Then show me the Upgrade of Mongo in the update_script, then we can remove it.
OVERLORD commented 2026-02-05 03:57:53 +03:00
Author
Owner
Copy Link

@JXF9527 commented on GitHub (Dec 11, 2025):

@MickLesk https://www.mongodb.com/docs/manual/release-notes/7.0-upgrade-standalone/

@JXF9527 commented on GitHub (Dec 11, 2025): @MickLesk https://www.mongodb.com/docs/manual/release-notes/7.0-upgrade-standalone/
OVERLORD commented 2026-02-05 03:58:00 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 11, 2025):

you dont understand? we dont update mongo in our scripts.

@MickLesk commented on GitHub (Dec 11, 2025): you dont understand? we dont update mongo in our scripts.
OVERLORD commented 2026-02-05 03:58:03 +03:00
Author
Owner
Copy Link

@JXF9527 commented on GitHub (Dec 11, 2025):

@MickLesk ok, thanks

@JXF9527 commented on GitHub (Dec 11, 2025): @MickLesk ok, thanks
OVERLORD commented 2026-02-05 03:58:05 +03:00
Author
Owner
Copy Link

@JXF9527 commented on GitHub (Dec 11, 2025):

This is the logic for upgrading MongoDB in the script:

function update_script() {
……

msg_info "Updating MongoDB"
if lscpu | grep -q 'avx'; then
MONGO_VERSION="8.0"
else
msg_error "No AVX detected (CPU-Flag)! We have discontinued support for this. You are welcome to try it manually with a Debian LXC, but due to the many issues with Omada, we currently only support AVX CPUs."
exit 10
fi

……
}

@JXF9527 commented on GitHub (Dec 11, 2025): This is the logic for upgrading MongoDB in the script: function update_script() { …… msg_info "Updating MongoDB" if lscpu | grep -q 'avx'; then MONGO_VERSION="8.0" else msg_error "No AVX detected (CPU-Flag)! We have discontinued support for this. You are welcome to try it manually with a Debian LXC, but due to the many issues with Omada, we currently only support AVX CPUs." exit 10 fi …… }
OVERLORD commented 2026-02-05 03:58:07 +03:00
Author
Owner
Copy Link

@JXF9527 commented on GitHub (Dec 11, 2025):

Oh sorry.. Just realized the upgrade logic has already been removed.

@JXF9527 commented on GitHub (Dec 11, 2025): Oh sorry.. Just realized the upgrade logic has already been removed.
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 not a script issue
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#2148
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?