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

Wrong Mongo version in Omada Update Script #1890

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

Originally created by @BunpGhost on GitHub (Oct 28, 2025).

✅ Have you read and understood the above guidelines?

yes

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

omada

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

update in lxc

⚙️ 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.14.11-4-pve)

📝 Provide a clear and concise description of the issue.

Hi, recently made a new install of Omada Controller. It went with trixie, all good.
Today tried running the update and have an error.
The source: /etc/apt/sources.list.d/mongodb-org-7.0.list keeps being added up to the list via the scrip in the https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.sh because mongo version is hard-coded to 7.0, but the installer uses 8.0.
Thank you

🔄 Steps to reproduce the issue.

run the update command inside the LXC.

❌ Paste the full error output (if available).

Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://deb.debian.org/debian trixie-updates InRelease
Hit:3 http://security.debian.org trixie-security InRelease
Hit:4 https://repos.azul.com/zulu/deb stable InRelease
Ign:5 http://repo.mongodb.org/apt/debian trixie/mongodb-org/7.0 InRelease
Hit:6 http://repo.mongodb.org/apt/debian bookworm/mongodb-org/8.0 InRelease
Err:7 http://repo.mongodb.org/apt/debian trixie/mongodb-org/7.0 Release
404 Not Found [IP: 52.222.132.70 80]
Error: The repository 'http://repo.mongodb.org/apt/debian trixie/mongodb-org/7.0 Release' does not have a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.

[ERROR] in line 41: exit code 0: while executing command $STD apt update

🖼️ Additional context (optional).

No response

Originally created by @BunpGhost on GitHub (Oct 28, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? omada ### 📂 What was the exact command used to execute the script? update in lxc ### ⚙️ 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.14.11-4-pve) ### 📝 Provide a clear and concise description of the issue. Hi, recently made a new install of Omada Controller. It went with trixie, all good. Today tried running the update and have an error. The source: /etc/apt/sources.list.d/mongodb-org-7.0.list keeps being added up to the list via the scrip in the https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.sh because mongo version is hard-coded to 7.0, but the installer uses 8.0. Thank you ### 🔄 Steps to reproduce the issue. run the update command inside the LXC. ### ❌ Paste the full error output (if available). Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian trixie-updates InRelease Hit:3 http://security.debian.org trixie-security InRelease Hit:4 https://repos.azul.com/zulu/deb stable InRelease Ign:5 http://repo.mongodb.org/apt/debian trixie/mongodb-org/7.0 InRelease Hit:6 http://repo.mongodb.org/apt/debian bookworm/mongodb-org/8.0 InRelease Err:7 http://repo.mongodb.org/apt/debian trixie/mongodb-org/7.0 Release 404 Not Found [IP: 52.222.132.70 80] Error: The repository 'http://repo.mongodb.org/apt/debian trixie/mongodb-org/7.0 Release' does not have a Release file. Notice: Updating from such a repository can't be done securely, and is therefore disabled by default. Notice: See apt-secure(8) manpage for repository creation and user configuration details. [ERROR] in line 41: exit code 0: while executing command $STD apt update ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 02:40:22 +03:00
OVERLORD commented 2026-02-05 02:40:36 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 29, 2025):

i only can fix the version mismatch, if you run your omada at debian 13 -> it cant work. Debian 13 hasnt Mongo-Repos.

Fixed with #8724

@MickLesk commented on GitHub (Oct 29, 2025): i only can fix the version mismatch, if you run your omada at debian 13 -> it cant work. Debian 13 hasnt Mongo-Repos. Fixed with #8724
OVERLORD commented 2026-02-05 02:40:40 +03:00
Author
Owner
Copy Link

@BunpGhost commented on GitHub (Oct 29, 2025):

i only can fix the version mismatch, if you run your omada at debian 13 -> it cant work. Debian 13 hasnt Mongo-Repos.

Fixed with #8724

The installer script, installed debian 13 by default. But probably used Bookworm repos for Mongo. Not a problem for me. Later, when there is a Mongo repo for debian, this update script should update it, right?

@BunpGhost commented on GitHub (Oct 29, 2025): > i only can fix the version mismatch, if you run your omada at debian 13 -> it cant work. Debian 13 hasnt Mongo-Repos. > > Fixed with [#8724](https://github.com/community-scripts/ProxmoxVE/pull/8724) The installer script, installed debian 13 by default. But probably used Bookworm repos for Mongo. Not a problem for me. Later, when there is a Mongo repo for debian, this update script should update it, right?
OVERLORD commented 2026-02-05 02:40:44 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 29, 2025):

It bumps to bookworm Debian Mongo Repo with our func.

@MickLesk commented on GitHub (Oct 29, 2025): It bumps to bookworm Debian Mongo Repo with our func.
OVERLORD commented 2026-02-05 02:40:52 +03:00
Author
Owner
Copy Link

@patcfly commented on GitHub (Oct 30, 2025):

Sorry for opening a duplicate. I also ran into this.

@patcfly commented on GitHub (Oct 30, 2025): Sorry for opening a duplicate. I also ran into this.
OVERLORD commented 2026-02-05 02:40:58 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 30, 2025):

If @CrazyWolf13 Approve the PR - maybe it fix it

@MickLesk commented on GitHub (Oct 30, 2025): If @CrazyWolf13 Approve the PR - maybe it fix it
OVERLORD commented 2026-02-05 02:41:03 +03:00
Author
Owner
Copy Link

@maz0r commented on GitHub (Nov 1, 2025):

Script is bombing out with the following [Deb 12 Bookwoorm]

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

   ✖️   APT update failed — invalid MongoDB repo for debian-bookworm? (Suite: bookworm)

[ERROR] in line 33: exit code 0: while executing command return 1

root@omada:~#
@maz0r commented on GitHub (Nov 1, 2025): Script is bombing out with the following [Deb 12 Bookwoorm] ``` ____ __ / __ \____ ___ ____ _____/ /___ _ / / / / __ `__ \/ __ `/ __ / __ `/ / /_/ / / / / / / /_/ / /_/ / /_/ / \____/_/ /_/ /_/\__,_/\__,_/\__,_/ ✖️ APT update failed — invalid MongoDB repo for debian-bookworm? (Suite: bookworm) [ERROR] in line 33: exit code 0: while executing command return 1 root@omada:~# ```
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
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#1890
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?