Problem with the update preparation for version 5.2

Hello,
When trying to prepare the release update to UCS 5.2, I received the following message:
root@bskw-s-2020:~# univention-upgrade

Starting univention-upgrade. Current UCS version is 5.0-9 errata1212

Checking for local repository: none
Checking for package updates: none
Checking for app updates: none
Checking for release updates: The update to UCS 5.1-0 is blocked because the component ‘opsi_20240925338247’ is marked as required.
none
How do I get the block solved opsi has already been completely uninstalled ?

Just did the upgrade on my 2 nodes from the UI panel.
Only an error message at the beginning, saying that there are 3 nagios configurations that are not supportet anymore: 24x7, WorkingHours, NonWorkingHours. Just deleted, and the upgrade works like a charm.

I have unfortunately the same issue.
I have 3 nodes and wanted to update them from 5.0-9 to 5.2

  • First, I removed the 3 nagios entries.
  • After that, I had to remove 5 SAML entries.
    Not it tells me that I don’t have the minimum version to upgrade.

Took me a while for figure out, that you need 5.0-9-1204 and I only have 5.0.9-1198.

Running the update command and trying to enforce --updateto 5.0-9-1204 just does nothing.

So I can’t install the path 1204 and I can’t update to 5.2

Any smarts tips here?

After some more digging, I figured that the only package with version 5.0-9-1198 was the univention-errata-level package. I ran

apt install univention-errata-level

and have no 5.0-9-1212. The updater is running now, crossing fingers that this will be good.

Moin,

I will try to answer some of the questions mentioned here.

First you are right, some legacy objects like Nagios entries have to be removed manually. We decided to not do this automatically to make it explicit that this is being removed now and custom configurations may need to be saved or solved with an alternative - But removing them is the right thing to do.

I understand your confusion, the command may be a bit misleading here: You cannot update to a certain erratum (the last number), but only to a certain patch level. The right parameter would be:

univention-upgrade --updateto 5.0-10  # or 5.0-99

Regards
Jan-Luca