Bug 40112

Summary:	sync_ldap may fail
Product:	UCS	Reporter:	Florian Best <best>
Component:	App Center	Assignee:	App Center maintainers <appcenter-maintainers>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	CC:	gohmann, wiesenthal
Version:	UCS 4.1
Target Milestone:	---
Hardware:	Other
OS:	Linux
What kind of report is it?:	Bug Report	What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	2: Will only affect a few installed domains	How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.034	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:
Bug Depends on:	40087
Bug Blocks:	40089

Description Florian Best

2015-11-26 12:17:02 CET

sync_ldap does a re-registration of apps if necessary. This reregistration sometimes create computer-objects for docker. This failed always before Bug #40087 and now only fails in case of SAML login.

It might be good to be able to give the established ldap connection to the appcenter library functions (or pass a callback). Also the Abort exception could raise have an attribute containing the original traceback and exception (Abort().exception = sys.exc_info()[0]; Abort().traceback = sys.exc_info()[2]).

+++ This bug was initially created as a clone of Bug #40087 +++

The UCS 4.1 App Center does not set repository/app_center/installed any longer.

On my UCS 4.1 test system:
root@master411:~# ucr search repository/app_center/installed
repository/app_center/installed:

root@master411:~# dpkg -l | grep -i univention-samba4
ii  univention-samba4                                   5.0.1-3.622.201511131352                     amd64        UCS - Samba4 integration package
ii  univention-samba4-sysvol-sync                       5.0.1-3.622.201511131352                     all          UCS - Samba4 sysvol synchronization
root@master411:~#

Comment 1 Stefan Gohmann

2019-01-03 07:22:36 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.