Description Dirk Ahrnke 2022-11-09 10:28:09 CET

Bug 50500 introduced the diagnostics module 901_ucsschool_import_counter

This will detect inconsistencies but doesnt tell how to fix them.

########################## Start 901_ucsschool_import_counter ##########################
## Check failed: 901_ucsschool_import_counter - UCS@school Import Counter Consistency ##
UCS@school stores internal counters for the next free username or mail address.
Inconsistencies in these counters can trigger erratic behaviour of the UCS@school import.

The following objects have faulty counter values:
  cn=weise.ric,cn=unique-usernames,cn=ucsschool,cn=univention,dc=training,dc=ucs
    - cn=weise.ric,cn=unique-usernames,cn=ucsschool,cn=univention,dc=training,dc=ucs: counter='1' but the value should be 2 or higher
    - cn=weise.ric,cn=unique-usernames,cn=ucsschool,cn=univention,dc=training,dc=ucs: usernames counter='1' but found user with uid weise.ric2
  cn=hoffmann.wil,cn=unique-usernames,cn=ucsschool,cn=univention,dc=training,dc=ucs
    - cn=hoffmann.wil,cn=unique-usernames,cn=ucsschool,cn=univention,dc=training,dc=ucs: usernames counter='3' but found user with uid hoffmann.wil3
########################### End 901_ucsschool_import_counter ###########################


This situation can happen if automatical assigment and manual administration are combined. 

At this time the knowledge how to fix the problem is only available internally and maybe limited to some persons. The methods vary by using ldapmodify/ldapvi or even some python-snippets. 

A diagnostics module should always show a supported way to fix a detected problem.