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

[dev.icinga.com #11083] Ensure that config sync updates are always sent on reconnect #3896

Closed
icinga-migration opened this issue Feb 4, 2016 · 2 comments
Milestone

Comments

@icinga-migration
Copy link
Member

@icinga-migration icinga-migration commented Feb 4, 2016

This issue has been migrated from Redmine: https://dev.icinga.com/issues/11083

Created by mfriedrich on 2016-02-04 10:30:07 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2016-02-04 10:35:04 +00:00)
Target Version: 2.4.2
Last Update: 2016-02-23 09:58:47 +00:00 (in Redmine)

Icinga Version: 2.4.1
Backport?: Already backported
Include in Changelog: 1

Currently updates including the replay log are only sent when the endpoint is not connected.

Changesets

2016-02-04 10:30:27 +00:00 by mfriedrich 949b129

Ensure that config sync updates are always sent on reconnect

fixes #11083

2016-02-08 12:06:15 +00:00 by (unknown) e13a652

Make sure the "syncing" attribute is set to false

refs #11083

2016-02-08 12:15:24 +00:00 by (unknown) e224e74

Make sure the "syncing" attribute is set to false

refs #11083

2016-02-23 08:35:47 +00:00 by mfriedrich a714225

Ensure that config sync updates are always sent on reconnect

fixes #11083

2016-02-23 08:35:57 +00:00 by (unknown) b3b2eb8

Make sure the "syncing" attribute is set to false

refs #11083
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Feb 4, 2016

Updated by mfriedrich on 2016-02-04 10:35:04 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset 949b129.

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Feb 23, 2016

Updated by gbeutner on 2016-02-23 09:58:47 +00:00

  • Backport? changed from Not yet backported to Already backported
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.