OPSI 4.3 May 2026 Release

[n.doerrer]

Dear opsi community,

we are pleased to announce the official release of the latest version of opsi today.

The May 2026 release of OPSI brings new features and important bug fixes, including security-related corrections. It is therefore recommended to apply the new server packages promptly.

Important note for environments using custom Python scripts or opsi-cli plugins: The Python package `opsicommon` has been replaced by the new package `opsi` https://github.com/opsi-org/python-opsi, which consolidates functionality from several previous packages. All existing functionality is still available, but has been moved to different modules. Anyone using custom scripts or plugins will need to update their imports accordingly.

Note on the Release Cycle:

Dear OPSI-User due to a new development approach we have adopted, we have adjusted our release cycle for feature releases accordingly. Effective immediately, feature releases will be published only every two months, on the last Wednesday of the month. The next feature release is scheduled for July 29, 2026.

Service releases (security fixes or important bug fixes) will continue to be released as needed at any time.

opsiconfd

This version includes security-related bug fixes and should be applied promptly. A new feature allows the dynamic depot selection algorithm to be configured individually per client. When restoring backups, existing database users can now be preserved by using the `--keep-current-users` option.

opsi-client-agent

The opsi-client-agent includes bug fixes and stability improvements. On Linux systems, compatibility of the notifiers with Wayland has also been improved. For linux systems using selinux we now install a configuration that enables using opsiclientd with active selinux.

opsi-configed

The process of creating new configs (host parameters) has been reworked and is now considerably more convenient. Several bugs have also been fixed: the reload in product groups works correctly again, group editing is fully functional again, and the installation status of netboot products is once again updated automatically.

opsi-cli

opsi-cli is now based on Python 3.14 and the new Python package `opsi` (see note above). Alongside bug fixes, this means that users with custom plugins will need to update them — alternatively, an older version of opsi-cli can be used in the meantime.

opensuse 16-0

We published the opensusel16-0 package, which enables installation of openSUSE Leap 16-0.

opsi-script

The command ExitScript no longer terminates opsi-script, but merely stops the execution of the product.

swaudit

We improved and extended software audit on macOS.



Packages for opsi 4.3 stable:

== OPSI_PACKAGE ==

• debian12 4.3.0.5-2 Changelog
• debian13 4.3.0.5-2 Changelog
• m-homebrew 5.1.8.0-9 Changelog
• opensusel15-5 4.3.1.1-1 Changelog
• opensusel15-6 4.3.1.1-1 Changelog
• opensusel16-0 4.3.1.1-1 Changelog
• opsi-cli 4.3.44.3-1 Changelog
• opsi-client-agent 4.3.19.9-1 Changelog
• opsi-configed 4.3.22.1-1 Changelog
• opsi-linux-client-agent 4.3.19.9-2 Changelog
• opsi-mac-client-agent 4.3.19.9-1 Changelog
• opsi-script 4.12.20.2-9 Changelog
• swaudit 4.3.2.3-1 Changelog

== SERVER_PACKAGE ==

• opsi-agent 4.3.18.3 Changelog
• opsi-tftp-hpa 5.2.9-7 Changelog
• opsi-utils 4.3.29.2 Changelog
• opsi-webgui 4.3.47.7 Changelog
• opsiconfd 4.3.53.8 Changelog

== TOOL ==

• opsi-cli 4.3.44.3 Changelog
• opsi-client-agent-msi 4.3.19.9-1 Changelog
• opsi-configed-portable 4.3.22.1 Changelog
• opsi-logviewer-portable 4.3.22.1 Changelog
• opsi-webgui.zip 4.3.47.7 Changelog

Your team at uib

[feltel]

Vielen vielen Dank, das ihr entgegen dem allgemeinen Trend die Releasezyklen wieder weitet statt sie zu straffen. Immer mehr Software erscheint in immer kürzeren Abständen. Das ist nicht nur nicht den Admins oder Usern zuträglich, sondern auch nicht der Softwarequalität. Ein zweimonatiger Zyklus ist mehr als ausreichend. It´s done when it´s done und nicht, wenn der Kalender es sagt.

[nicolaslebrun]

Hallo,

On up to date OPSI server, with opsi-utils version 4.3.29.2-1, if I launch opsi-python, the "import opsicommon" still works and "import opsi" doesn't.

Am I missing something ? Am I misunderstanding the change ?

Regards
Nico

[n.doerrer]

Hello,

opsi-utils 4.3.29.2-1 still contains opsicommon and not the new opsi library. But this will change with the next feature release.
If you want to use the new library already, you can use `opsi-cli python` instead of `opsi-python`.

[j.schneider]

Dear opsi community,

we are pleased to announce the official release of the latest version of opsi today.

This service release fixes several issues in the opsi-client-agent:

• A timing issue during Windows startup could cause actions to start too early, before the GUI had finished loading.
• Popup notifications now work as expected again.
• Timer events configured with both a start interval and an interval could, under certain circumstances, be executed twice.

In addition, this release fixes a minor issue in opsiconfd that caused not all checks to be executed during the health check.




Packages for opsi 4.3 stable:

== OPSI_PACKAGE ==

• opsi-client-agent 4.3.19.11-1 Changelog

== TOOL ==

• opsi-client-agent-msi 4.3.19.11-1 Changelog

== SERVER_PACKAGE ==

• opsiconfd 4.3.53.9 Changelog

Your team at uib