Seen in ipa-healthcheck.
If 389-ds isn't running then /bin/systemctl is-active ipa-dnskeysyncd.service returns "activating". Called from ipaplatform this is taken as "the service is still starting" and it loops.
stderr= Calling check Starting external process args=['/bin/systemctl', 'is-active', 'ipa-custodia.service'] Process finished, return code=0 stdout=active
stderr= Calling check Starting external process args=['/bin/systemctl', 'is-active', 'ipa-dnskeysyncd.service'] Process finished, return code=3 stdout=activating
... repeat a ton of times
Metadata Update from @frenaud: - Issue set to the milestone: DNSSEC