Any plans to Upgrade Odoo 16?

App
,
1

Thanks to everyone that has put in time and effort to make NS8 what it is today.

I am still mucking about with it in a lab and recently installed Odoo. I observe that the version of Odoo bundled with NS8 is Odoo 16. I have two questions I’d need some guidance with:

  1. Is it possible for me to update my version to Odoo 17/18/19 Community Edition? I am doing some labs where I’m building some CTI with Asterisk and Odoo and would like to work with the most recent available version of Odoo.

  2. Can I add custom modules (mostlyOdoo Community Association (OCA) modules on GitHub) to NS8 instance of Odoo? I’m looking to add some of the VoIP modules to test VoIP integration with Odoo CE.

Thanks in advance
airsay

NS8 Odoo Module Available
2

Let’s ask @Gian8
See also https://community.nethserver.org/t/ns8-odoo-module-available for more information.

3

Thanks. I will move the conversation over there.

1 Like
4

@mrmarkuz is there an equivalent post/thread for ERPNext?

5

Yes, but there are different approaches:

You can search for appname #App in the search bar to find the threads, for example Search results for 'erpnext #App order:latest' - NethServer Community

1 Like
6

Hello all.

Don’t mean to hijack this thread, however I am trying to install Odoo on my NS8 instance, I get that there is no stable version available.

image
image1202×722 46.6 KB

Does anyone know how I can get previous stable versions, or when the next stable version will be released?

7

That question has been asked before. It seems the Nethsesis partner Innovyou is unresponsive?

cc: @Gian8 @alefattorini

8

Hi all,

just to give some context from a recent discussion we had with Innovyou. The current Odoo 16 community app should be considered a one-off release and there is no plan for an automatic upgrade path on that base. This is mainly due to the well-known complexity of Odoo upgrades when addons and customizations are involved, where a blind in-place update would very likely break existing installations.

Innovyou confirmed their interest in continuing the project on NS8 and the focus is now on a new app based on Odoo 18, with the intention of keeping it maintained for the whole lifecycle of that major version. The goal is to make it again available through NethForge.

As for existing Odoo 16 installations, the discussion is around a possible manual and documented upgrade procedure, if it turns out to be technically feasible and reliable. In any case, automatic upgrades from 16 will be explicitly blocked to avoid unexpected disruptions.

Although Odoo 16 is end-of-life and its use is discouraged :warning:, it is still technically possible to install it on a specific cluster node from the command line. The node ID (for example, 2) can be found in the Nodes page. To install Odoo 16 on cluster node NODE_ID, you can run:

add-module ghcr.io/innovyou/odoo:1.0.2 NODE_ID

Innovyou is aware of the open questions in this thread. They should be able to provide more details and timelines as soon as their development plans are clearer.

4 Likes
9

Any news on this please?

1 Like
11

I think this kind of wording is unnecessarily aggressive and does not help the discussion.

Please also note that Odoo is not a Nethesis product and no paid relationship exists in your case. Community integrations and compatibility discussions should not be interpreted as a commercial guarantee or endorsement.

Constructive feedback, technical details, and reproducible issues are always welcome. Personal attacks and legal threats directed at companies or individuals are not.

1 Like
12

Nothing wrong with rocking the boat is bit.

In other words, ‘you’ are not a Nethesis customer nor a partner.

It is not perfect world, just like the real world, but using wording like ‘agressive’, ‘personal attacks’ and ‘legal threats’ seem strategically chosen to set a artificial sentiment.

Anyway, nothing on the Odoo subject?

13

if you’re interested a great feature rich ERP solution for your business, kindly, consider erpnext, we have bene very consistent in upgrades, and have managed upgrades between major versions as well.

We even replicated the entire frappe cloud within Nethserver, if you’re daring enough, ad need to scale.

Other than that, Supporting a fully features erp system, is not as easy as you might think and alot of things could go wrong and break.

We are lucky and happy that we have afew paying customers, who enable is to continue supporting these kinds of efforts.

1 Like
14

The challenge with ERPNext is the “high bar” to get started. You literally need to have a CoA setup and properly configured before you can start using it. With Odoo, you can get started with one module and when you see value, you can then consider a full scale accounting implementation. ERPNext is great, but that need for a CoA was and still is off putting for me

15

What one app do you mean, Frappe CRM, is seprate from erpnext, doesnt need Charts of Accounts.
same applies, to HelpDesk, and many other Apps.

Its when you need accounting, that you really need erpnext, ofcourse for proper accounting Charts of Accounts, needs to be properly configured. as with any system, including quickbooks. Default are always there, and you can link to them, but i doubt youd want to do that.

16

Have they spun those of to be standalone apps? CRM and Helpdesk?

17

I ended up installing an odoo 17 from scratch on a Debian and restored then upgraded the v16 DB with OpenUpgrade.

Not a trivial task at all. Multiple OpenUpgrade passes are generally necessary with manual fixes between each run.

My notes just in case :

apt install -y locales
sed -i ‘s/# fr_BE.UTF-8 UTF-8/fr_BE.UTF-8 UTF-8/’ /etc/locale.gen
locale-gen
update-locale LANG=fr_BE.UTF-8 LC_ALL=fr_BE.UTF-8

apt install -y sudo vim less curl wget unzip gnupg leave ncdu mc rsync

apt install -y 
git build-essential 
python3 python3-dev python3-pip python3-venv python3-setuptools python3-wheel 
libzip-dev libxslt1-dev libldap2-dev libsasl2-dev libpq-dev 
libjpeg-dev libtiff5-dev libopenjp2-7-dev zlib1g-dev 
libxml2-dev libfreetype6-dev fontconfig 
nodejs npm node-less 
wkhtmltopdf xfonts-75dpi xfonts-base

npm install -g rtlcss

apt install -y postgresql
systemctl enable postgresql
systemctl start postgresql
systemctl status postgresql
su - postgres -c “createuser -s odoo”

useradd -m -d /opt/odoo17 -U -r -s /bin/bash odoo17

su - odoo
cd /opt/odoo
git clone https://github.com/odoo/odoo.git --branch 17.0 --depth 1

python3 -m venv venv
source venv/bin/activate

pip install --upgrade pip wheel setuptools
pip install -r odoo/requirements.txt

cat > /etc/odoo.conf <<‘EOF’
[options]
; ---- Directories ----
addons_path = /opt/odoo17/odoo/addons
data_dir = /var/lib/odoo

; ---- Database ----
db_host = False
db_port = False
db_user = odoo
db_password = False

; ---- Server ----
xmlrpc_port = 8069
logfile = /var/log/odoo/odoo.log
proxy_mode = True
EOF

mkdir -p /var/lib/odoo /var/log/odoo
chown -R odoo:odoo /var/lib/odoo /var/log/odoo /etc/odoo.conf
chmod 640 /etc/odoo.conf

cat > /etc/systemd/system/odoo.service <<‘EOF’
[Unit]
Description=Odoo 17 ERP
After=network.target postgresql.service

[Service]
Type=simple
User=odoo
Group=odoo
ExecStart=/opt/odoo17/venv/bin/python3 /opt/odoo17/odoo/odoo-bin -c /etc/odoo.conf
Restart=always

[Install]
WantedBy=multi-user.target
EOF

# IMPORT ODOO 16 Database

su - postgres -c “createdb -E UTF8 -T template0 -O odoo "Odoo"”
su - postgres -c “psql -d Odoo -f /chemin/vers/Odoo.sql”
su - postgres -c “psql -c ‘ALTER DATABASE "Odoo" OWNER TO odoo;’”

# RESTORE Filestore

mkdir -p /var/lib/odoo/.local/share/Odoo/filestore/
rsync -av ~/Odoo_2025-11-08_15-49-44/filestore/ /var/lib/odoo/.local/share/Odoo/filestore/Odoo/
chown -R odoo:odoo /var/lib/odoo/.local/share/Odoo

# INSTALL OpenUpgrade and MIGRATE

su - odoo
cd /opt/odoo17
git clone https://github.com/OCA/OpenUpgrade.git -b 17.0 openupgrade
source venv/bin/activate
pip install -r openupgrade/requirements.txt
deactivate

cd /opt/odoo17
source venv/bin/activate
./venv/bin/python3 odoo/odoo-bin 
-c /etc/odoo.conf 
-d Odoo 
–update=all 
–stop-after-init 
–load=base,web,openupgrade_framework 
–addons-path=/opt/odoo17/odoo/addons,/opt/odoo17/openupgrade 
–upgrade-path=/opt/odoo17/openupgrade/openupgrade_scripts/scripts 
–logfile=/var/log/odoo/openupgrade.log
deactivate
1 Like
18

Please help add the font NotoSansTC.ttf to odoo.
Thanks

19

Friday is may day off - and I can use up my AI token for free rather wasting the daily limit … We (claude and I) would be willing to fill the gap:

The official Odoo app is marked obsolete on the wiki (“do not install”) and is
stuck on Odoo 16 (end of life). Rather than wait, we can offer an independent,
self-built community module for a current Odoo Community release.

We already ran an unpublished feasibility on our dev node and it works:

  • Odoo 19.0 Community from the official image, with PostgreSQL 16
  • a fresh database initialises cleanly and the web UI serves the login
  • a custom addons directory is picked up (a test module dropped into
    /mnt/extra-addons was in Odoo’s addons_path immediately), so OCA and
    in-house modules can be added — this was the second question in this thread

What the module would provide (v1.0.0, Odoo 19 Community):

  • one Odoo container + one PostgreSQL container, rootless like our other modules
  • a single Traefik route with Let’s Encrypt for the web UI, plus the
    websocket/longpolling endpoint for live chat and notifications
  • persistent volumes for the database and the filestore
  • an admin master password for the database manager
  • a custom-addons folder the admin populates with OCA / own modules
  • backup and restore of the database and filestore in the NS8 backup

Scope and honesty:

  • Community edition only, self-built from the official image; unofficial, not
    affiliated with Odoo or Nethesis, and clearly labelled as such. It would
    coexist with any future official Odoo 18/19 app from Innovyou.
  • No automatic 16 → 19 upgrade. Odoo major upgrades with addons are fragile;
    we deliver a clean current install, not an in-place migration.
  • LDAP login is an OCA/Enterprise topic in Odoo, so not in v1; it can be added
    later through the addons folder.

Rough effort for a solid v1.0.0: about one working week, then published to our
repository like our other 18 modules, with pinned version and weekly upstream
checks.

If there’s interest, tell us which version you’d prefer (we lean to 19, 18 is possible, too) and any
must-have addons, and we’ll get the first build onto our repository.

3 Likes
20

I’ll try someday ! Thank you :slight_smile:

21

I hope you use GitHub - NethServer/agents: Agents skills and conventions · GitHub