Problem: UCS 5.2 Upgrade fails Due to required legacy OX Components

Knowledge Base Community
, , ,
1

Summary

During preparation for an upgrade to UCS 5.2, it was discovered that systems with a previously installed OX App Suite may fail the upgrade path, even though OX packages were intentionally removed and the App Center no longer lists OX as installed.

The upgrade is blocked because a legacy OX repository component is still marked as required in UCR, originating from an earlier OX installation that used packages which have since been discontinued.

Problem

The system has a functional mail and OX-related setup. However, on 2024-07-23, the following OX packages were automatically removed, most likely during a regular univention-upgrade:

Remove: univention-ox-meta-singleserver:amd64 (12.0.41), \
        open-xchange-pns-mobile-api-facade:amd64 (7.10.6-61), \
        univention-ox-mobile-api-facade:amd64 (12.0.41)

As a result:

  • The App Center no longer detects an installed OX App Suite:
root@mail01:~# univention-app info
UCS: 5.0-10 errata1362
Installed: fetchmail=6.3.26 mailserver=12.0 ox-connector=2.3.5 prometheus-node-exporter=2.0.1
Upgradable:
  • Nevertheless, univention-upgrade still detects a required OX component and blocks the upgrade:
The update to UCS 5.1-0 is blocked because the component 'oxseforucs_20231106074516' is marked as required.

Root Cause

The issue is caused by legacy OX repository components that remain enabled in UCR from an earlier OX installation.

The removed packages are no longer available or maintained:

  • univention-ox-meta-singleserver
  • univention-ox-mobile-api-facade

OX officially discontinued the Mobile API Facade. As documented in later OX versions, the package was removed and its configuration migrated into univention-ox:

* Remove univention-ox-mobile-api-facade as a package.
  OX has discontinued the mobile API facade.

Due to the historical installation and outdated component versions, UCS still considers the legacy OX repository component as required, which blocks the upgrade to UCS 5.1 and later.

Investigation

Check the configured online repository components:

ucr search --brief repository/online/component/

On affected systems, a legacy OX component similar to the following is present (version may differ):

repository/online/component/oxseforucs_20231106074516: enabled
repository/online/component/oxseforucs_20231106074516/version: current
repository/online/component/oxseforucs_20231106074516/server: https://appcenter.software-univention.de

On healthy or updated systems, a newer component identifier is typically used, for example:

repository/online/component/oxseforucs_20240306095834: enabled
repository/online/component/oxseforucs_20240306095834/version: current
repository/online/component/oxseforucs_20240306095834/server: https://appcenter.software-univention.de
repository/online/component/oxseforucs_20240306095834/description: OX App Suite

Solution

The recommended solution is to reinstall the OX App Suite via the App Center, which correctly registers the required repository component:

univention-app install oxseforucs

After installation, rerun the upgrade check. The blocking component should now be resolved and the UCS upgrade can proceed.

Workaround

In some cases, the upgrade may still be blocked even after installing the OX App Suite.

  1. Ensure all OX-related package updates are available and applied:
  • apt-get update
  • apt list --upgradable
  • univention-upgrade --ignoressh --updateto 5.0-999
  1. If no updates are pending and the upgrade remains blocked, the legacy repository component can be manually disabled:
  • ucr set repository/online/component/oxseforucs_20231106074516=disabled

After disabling the obsolete component, rerun univention-upgrade.

  • univention-upgrade --ignoressh --updateto 5.2-0

Note: This workaround should only be used if OX is intentionally no longer required or after verifying that a current OX App Suite installation is present.

Conclusion

Legacy OX repository components from discontinued packages can persist in UCR and block UCS upgrades, even when OX is no longer visible in the App Center. Reinstalling the OX App Suite or disabling obsolete components resolves the issue and allows the upgrade path to UCS 5.2 to proceed.

Check also:

and: