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 #12179] Duplicate messages for command_endpoint w/ master and satellite #4375

Closed
icinga-migration opened this issue Jul 19, 2016 · 6 comments

Comments

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

commented Jul 19, 2016

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

Created by mfriedrich on 2016-07-19 15:37:28 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2016-07-19 15:40:05 +00:00)
Target Version: 2.5.0
Last Update: 2016-07-27 20:14:02 +00:00 (in Redmine)

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

  • 1 Master
  • 2 Satellites

"satellite" Zone with local configuration, checks are scheduled by satellite endpoints.
command_endpoint is used to "pin" checks to those endpoints.

problem:

  • the master receives a check result from s1 which got executed as command_endpoint
  • master relays check result back to the satellite zone (bug)

Changesets

2016-07-19 15:36:14 +00:00 by mfriedrich 3d06df9

Fix duplicate CheckResult messages for command_endpoint

fixes #12179

2016-07-19 16:32:01 +00:00 by gbeutner 9075de6

Fix message routing for command_endpoint checks in satellite zones with >2 instances

refs #12179

2016-07-29 08:17:37 +00:00 by mfriedrich e0c3f43

Fix duplicate CheckResult messages for command_endpoint

fixes #12179

2016-07-29 08:17:38 +00:00 by gbeutner b4589ab

Fix message routing for command_endpoint checks in satellite zones with >2 instances

refs #12179

Relations:

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 19, 2016

Updated by mfriedrich on 2016-07-19 15:40:05 +00:00

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

Applied in changeset 3d06df9.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 19, 2016

Updated by mfriedrich on 2016-07-19 15:43:33 +00:00

  • Description updated
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 19, 2016

Updated by mfriedrich on 2016-07-19 17:58:12 +00:00

  • Priority changed from Normal to High
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 25, 2016

Updated by gbeutner on 2016-07-25 07:45:29 +00:00

  • Duplicated set to 11196
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 25, 2016

Updated by gbeutner on 2016-07-25 07:46:16 +00:00

  • Duplicated set to 11041
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 27, 2016

Updated by mjbrooks on 2016-07-27 20:14:02 +00:00

Great work guys.

Is this going to be backported for 2.4.x? Point releases require a lot of movement/QA/Etc for one of my clients and they need this ASAP.

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.