Event queue is not working

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49332

• Created at 2017-07-25 10:57:27 by tbordaz (@tbordaz)
• Closed at 2017-07-26 10:43:22 as fixed
• Assigned to tbordaz (@tbordaz)

---

Issue Description

The change for 49316 (clock unsafety) is breaking the loop of the eventq that continuously sleeps without calling the recorded events

Package Version and Platform

Steps to reproduce

1. It can be detected recording event (like retroCL trimming) and noticing they are not called

Actual results

Recorded periodic event (likely also fixed time event) are not called

Expected results

Call the recorded event

[389-ds-bot]

Comment from tbordaz (@tbordaz) at 2017-07-25 11:07:11

[389-ds-bot]

Comment from tbordaz (@tbordaz) at 2017-07-25 11:07:12

Metadata Update from @tbordaz:

• Custom field component adjusted to None
• Custom field origin adjusted to None
• Custom field reviewstatus adjusted to None
• Custom field type adjusted to None
• Custom field version adjusted to None

[389-ds-bot]

Comment from tbordaz (@tbordaz) at 2017-07-25 11:08:08

Metadata Update from @tbordaz:

• Custom field reviewstatus adjusted to review (was: None)

[389-ds-bot]

Comment from tbordaz (@tbordaz) at 2017-07-25 11:08:26

Metadata Update from @tbordaz:

• Issue assigned to tbordaz

[389-ds-bot]

Comment from tbordaz (@tbordaz) at 2017-07-25 11:09:38

Metadata Update from @tbordaz:

• Issue set to the milestone: 1.3.7.0

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2017-07-25 23:55:31

Metadata Update from @Firstyear:

• Custom field reviewstatus adjusted to ack (was: review)

[389-ds-bot]

Comment from tbordaz (@tbordaz) at 2017-07-26 10:35:31

git push origin master

Counting objects: 6, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 877 bytes | 0 bytes/s, done.
Total 6 (delta 4), reused 0 (delta 0)
remote: Sending to redis to log activity and send commit notification emails
remote: Emitting a message to the fedmsg bus.
remote: * Publishing information for 1 commits
remote: Sending notification emails to: 389-commits@lists.fedoraproject.org
To ssh://git@pagure.io/389-ds-base.git
   28ad77e..af536ea  master -> master

[389-ds-bot]

Comment from tbordaz (@tbordaz) at 2017-07-26 10:43:22

Metadata Update from @tbordaz:

• Issue close_status updated to: fixed
• Issue status updated to: Closed (was: Open)