Univention Bugzilla – Bug 47381
notifier stopped during import dry-run
Last modified: 2019-08-05 18:42:01 CEST
notifier stopped during import dry-run At least for me that isn't the behavior I expect from a dry-run. The notifier should not be stopped since it should not be necessary to stop it during a dry-run.
ACK. Adding dependency on Bug #47203, so we can be sure a dry-run commits no changes to LDAP. (The read-only cn=admin connection is *much* faster than the unprivileged connection provided by get_unprivileged_connection(), as it bypasses all ACLs.)
In a dry-run, the notifier won't be stopped anymore. [dtroeder/47381_no.notifier.stop.in.dry.run 396f65378] Bug #47381: don't stop notifier in import dry-run Please reopen, if you want to QA this and it should be merged, built and an advisory written.
[4.4] 7c6e5bb51 Bug #47381: don't stop notifier in import dry-run [4.4] 2d2a18089 Bug #47381: Merge branch 'dtroeder/47381_no.notifier.stop.in.dry.run' into 4.4 [4.4] 5ce5a78db Bug #47381: changelog [4.4] 8702a3da6 Bug #47381: advisory ucs-school-import (17.0.6-23)
[4.4 866df0f9e] Bug #47381: rename noop -> nullcontext [4.4 fe12e2a01] Bug #47381: yaml What I tested: ucs-school-user-import dry-run -> notifier is not stopped -> OK ucs-school-user-import -> notifier is stopped -> OK 34_import-users-legacy -> OK 34_import-users_via_python_api -> OK 235_import-users_dry-run-support_in_pyhooks -> Verified
UCS@school 4.4 v3 has been released. https://docs.software-univention.de/release-notes-ucsschool-4.4v3-de.html If this error occurs again, please clone this bug.