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 #12417] IDO does duplicate config updates #4471

Closed
icinga-migration opened this issue Aug 13, 2016 · 2 comments

Comments

Projects
None yet
1 participant
@icinga-migration
Copy link
Member

commented Aug 13, 2016

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

Created by gbeutner on 2016-08-13 20:31:54 +00:00

Assignee: gbeutner
Status: Resolved (closed on 2016-08-13 21:00:05 +00:00)
Target Version: 2.5.0
Last Update: 2016-08-13 21:00:05 +00:00 (in Redmine)

Icinga Version: 2.4.10
Backport?: Not yet backported
Include in Changelog: 1

  1. Ido{Mysql,Pgsql}Connection::Reconnect: for loop (SendConfigUpdate)
  2. Ido{Mysql,Pgsql}Connection::Reconnect: DeactivateObject
  3. ConfigObject::RestoreObject calls SetVersion() - which triggers yet another config update
  4. DbConnection: ConfigObject::OnActiveChanged calls UpdateObject

Changesets

2016-08-13 20:55:11 +00:00 by gbeutner abe125b

Avoid duplicate IDO config updates at startup

fixes #12417

2016-08-13 21:07:18 +00:00 by gbeutner 8425edb

Avoid duplicate IDO config updates at startup

fixes #12417

2016-08-13 21:31:22 +00:00 by gbeutner ed53366

Avoid duplicate IDO config updates at startup

fixes #12417
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Aug 13, 2016

Updated by gbeutner on 2016-08-13 20:47:40 +00:00

  • Description updated
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Aug 13, 2016

Updated by gbeutner on 2016-08-13 21:00:05 +00:00

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

Applied in changeset abe125b.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.