[dev.icinga.com #12707] Director destroys Icinga Replication

[icinga-migration]

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

Created by siegfried on 2016-09-12 13:29:15 +00:00

Assignee: siegfried
Status: Closed (closed on 2016-10-11 15:01:52 +00:00)
Target Version: (none)
Last Update: 2016-10-11 15:01:52 +00:00 (in Redmine)

---

After deployment of configuration files with Director, Icinga2 Replication is dis functional. Only after icinga2 replication full reset and restart off all icinga2 nodes and agents, replication is starting again.

reset means delete of
/var/lib/icinga2/api/packages
/var/lib/icinga2/api/zones
and restart of all nodes an agents

---

Relations:

• relates #10000

[icinga-migration]

Updated by tgelf on 2016-09-12 13:33:43 +00:00

• Relates set to 10000

[icinga-migration]

Updated by tgelf on 2016-09-12 13:39:15 +00:00

• Tracker changed from Bug to Support
• Status changed from New to Feedback
• Assigned to set to siegfried

When Icinga 2 is unable to restart after a deployment this is probably because of the linked Icinga 2 bug. Could you please provide me some more details on how you are able to reproduce this? I'm using Director massively in clustered environments and never experienced this so far.

The only scenario I could imagine were additional Zones added / removed and deployed through Director. However, that's something that mostly wouldn't work anyways just of how Icinga 2 works internally. So here please let me know what you're trying to build, what you're doing to reproduce this error, eventually I could help you.

There are some related hints in the "How it works" documentation (https://github.com/Icinga/icingaweb2-module-director/blob/master/doc/10-How-it-works.md), but those already presuppose good understanding of the Icinga 2 clustering mechanism.

Cheers,
Thomas

[icinga-migration]

Updated by tgelf on 2016-10-11 15:01:52 +00:00

• Status changed from Feedback to Closed

No response since a month, closing this as a non-issue. Does not happen when not doing hackish operations on zones/endpoints and when following the docs. And the core issue here is #10000, there is nothing Director can do about this.