Univention Bugzilla – Bug 56072
App Listener should handle unreadable objects by ignoring it consequently
Last modified: 2023-05-31 15:38:01 CEST
If an object changed in LDAP, the listener creates a file that has the entryUUID in it. This file is picked up by the listener-converter. It may be that this process may not read the object. This can happen due to LDAP/UDM differences (see Bug#55216) or due to explicit ACL rules for the machine account of the App. Anyway, we should handle not being able to read the object and log that once. But then remove the file forever (and log that, too).
Package: univention-appcenter Version: 9.0.7-9 Branch: ucs_5.0-0 Scope: errata5.0-3 univention-appcenter.yaml 8a43ccac9f00 | Bug #56072: yaml 0112ae819ea9 | Bug #56072: remove listener file when corresponding udm object cannot be identified The App Center listener now removes files from its queue that contain entryUUIDs whose corresponding UDM objects cannot be found. These files cannot be processed by the listener and would otherwise remain in the queue forever and cause infinite error logging.
QA: The files are removed when the object is not found in UDM: OK yaml: OK changelog: OK
In Jenkins there is a traceback: Traceback (most recent call last): File "/usr/share/ucs-test/20_appcenter/100_settings.py", line 262, in test_string_custom_setting_docker os.remove(custom_settings_file) FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/univention-appcenter/apps/apache/custom.settings'
The errors from yesterday's jenkins test run are unrelated to this bug. There was a connection issue with the app center which caused some problems. The latest test runs do not contain any failed appcenter tests anymore. I also executed the tests on a test vm and they were successful. I will change the bug status back to resolved fixed.
<https://errata.software-univention.de/#/?erratum=5.0x693>