Bug 56134 – Prevent UCS 5.1 Upgrade if there are still legacy UDM objects/modules

Bug 56134 - Prevent UCS 5.1 Upgrade if there are still legacy UDM objects/modules


Summary:	Prevent UCS 5.1 Upgrade if there are still legacy UDM objects/modules

Status:	VERIFIED FIXED

Product:	UCS
Classification:	Unclassified
Component:	UDM (Generic)
Version:	UCS 5.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 5.1
Assigned To:	Florian Best
QA Contact:	Iván.Delgado

URL:
Keywords:

Depends on:	56765 52048 56367 56651 56820 56824
Blocks:
	Show dependency tree / graph

Reported:	2023-06-09 14:53 CEST by Florian Best
Modified:	2024-03-08 11:02 CET (History)
CC List:	2 users (show)

See Also:	52048 56367
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Florian Best

2023-06-09 14:53:01 CEST

As we did for UCS 5.0 we should also do for UCS 5.1/UCS 5.2 to block the upgrade as long as there are objects in LDAP for legacy UDM modules.

Legacy UDM modules are at least:
settings/portal*

Comment 1 Florian Best

2023-06-20 21:06:35 CEST

See also Bug #52048

Comment 3 Florian Best

2023-10-23 20:54:28 CEST

settings/portal*: Bug #52048
uvmm/*: Bug #56651
nagios/timeperiod: Bug #56367
saml/* and oidc/rpservice: Bug #56765

Comment 4 Iván.Delgado

2023-11-15 16:47:37 CET

OK: code review
OK: upgrade to 5.2 from 4.4 is blocked if any object exist
OK: changelog

Comment 5 Florian Best

2024-03-08 11:02:57 CET

univention-updater (16.0.4)
221e98053151 | feat(updater): add preup check to remove obsolete objects