Removed PR_DISPLAY_TYPE_EX lead to errors in mbop, ldap-downsync, etc.

[crpb]

I guess this was this commit d0cad7d [Delete user properties if not present in LDAP]??

root@grom-test-2:~# cat /var/log/zypp/history  |grep 2026-04-30 |grep admin-api
2026-04-30 16:34:35|install|grommunio-admin-api|1.18.17.m1b402b4-lp160.12.1|noarch||grommunio|13027e8e06f5ff6d45a0185e303e22156c8c7cbeb91045d3a8b640f2738fec56|
root@grom-test-2:~# journalctl -S -1month -u grommunio-ldap-sync -p 3 --no-hostname
Apr 30 21:06:47 systemd[1]: Failed to start Grommunio LDAP Sync.
May 01 00:05:39 systemd[1]: Failed to start Grommunio LDAP Sync.
May 01 03:06:20 systemd[1]: Failed to start Grommunio LDAP Sync.
May 01 06:06:01 systemd[1]: Failed to start Grommunio LDAP Sync.
May 01 09:06:42 systemd[1]: Failed to start Grommunio LDAP Sync.
-- Boot 612c1680150c4975b15d90a7d1c53d64 --
May 01 11:05:53 systemd[1]: Failed to start Grommunio LDAP Sync.
-- Boot 4298267ed5504bcdad3d34403e66181a --
May 01 12:05:16 systemd[1]: Failed to start Grommunio LDAP Sync.
May 01 15:05:57 systemd[1]: Failed to start Grommunio LDAP Sync.
May 01 18:06:18 systemd[1]: Failed to start Grommunio LDAP Sync.
May 01 21:05:42 systemd[1]: Failed to start Grommunio LDAP Sync.
May 02 00:05:42 systemd[1]: Failed to start Grommunio LDAP Sync.
May 02 03:05:23 systemd[1]: Failed to start Grommunio LDAP Sync.
May 02 06:06:52 systemd[1]: Failed to start Grommunio LDAP Sync.

Since yesterday the missing property 956628995 is breaking things in multiple places.

What doesn't work/breaks?

• grommunio-admin ldap downsync ...

root@grom-test-2:~# grommunio-admin ldap downsync --complete --force --organization 1
Synchronizing info@crpb.de...success
Synchronizing dk@crpb.de...success
Synchronizing jg@crpb.de...(ldap@default) KeyError('displaytypeex')
An error occurred: KeyError('displaytypeex').

• gromox-mbop

root@grom-test-2:~# grommunio-admin user query  |wc -l
28
root@grom-test-2:~# gromox-mbop foreach.here echo-username | wc -l
mysql_adaptor: There are 8 users with no PR_DISPLAY_TYPE_EX set, which makes their existence _undefined_.
18

yes, user-query has two additional lines with ID, and "admin" so those numbers make sense.

I can see that the DISPLAYTYPEEX isn't set in the mysqltable as this command lists me multiple mails with missing displaytypeex's.

QUERY='SELECT * FROM user_properties where user_properties.proptag IN (956628995,972947487) ORDER BY user_properties.user_id;' ; mariadb -D grommunio --execute "$QUERY"

The only solution is either recreate all borked users which is not a problem here as it's just throw-away stuff or inserting those missing entries with a default "0" to make things work again. e.g. INSERT INTO user_properties VALUES (3, 956628995, 1, NULL, 0);

enough for now..