Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

periodic dirsync timed event causes server to loop repeatedly #440

Closed
389-ds-bot opened this issue Sep 12, 2020 · 3 comments
Closed

periodic dirsync timed event causes server to loop repeatedly #440

389-ds-bot opened this issue Sep 12, 2020 · 3 comments
Labels
closed: fixed Migration flag - Issue
Milestone

Comments

@389-ds-bot
Copy link

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


If the sync agreement is changed at the same time as the periodic dirsync event queue task is triggered, the server will loop repeatedly because the EVENT_RUN_DIRSYNC case is not handled in the STATE_WAIT_WINDOW_OPEN state.

@389-ds-bot 389-ds-bot added the closed: fixed Migration flag - Issue label Sep 12, 2020
@389-ds-bot 389-ds-bot added this to the 1.2.11.12 milestone Sep 12, 2020
@389-ds-bot
Copy link
Author

Comment from rmeggins (@richm) at 2012-08-28 02:40:31

0001-Ticket-440-periodic-dirsync-timed-event-causes-serve.patch
0001-Ticket-440-periodic-dirsync-timed-event-causes-serve.patch

@389-ds-bot
Copy link
Author

Comment from rmeggins (@richm) at 2012-08-28 08:01:55

c96c3e5..cd7d059 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit changeset:cd7d059ec080bf0a783272d6a0ea625c99b2f7f3/389-ds-base
Author: Rich Megginson richm@redhat.com
Date: Fri Aug 24 13:30:43 2012 -0600
ef63c61..6cfc1c0 master -> master
commit changeset:6cfc1c0ac84200535a512dd4ef28fc9dd82d6c18/389-ds-base
Author: Rich Megginson richm@redhat.com
Date: Fri Aug 24 13:30:43 2012 -0600

@389-ds-bot
Copy link
Author

Comment from rmeggins (@richm) at 2017-02-11 23:03:47

Metadata Update from @richm:

  • Issue assigned to richm
  • Issue set to the milestone: 1.2.11.12

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: fixed Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant