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 #8213] HA-Setup with update-config #2516

Closed
icinga-migration opened this issue Jan 14, 2015 · 12 comments
Closed

[dev.icinga.com #8213] HA-Setup with update-config #2516

icinga-migration opened this issue Jan 14, 2015 · 12 comments
Labels
area/distributed enhancement

Comments

@icinga-migration
Copy link
Member

icinga-migration commented Jan 14, 2015

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

Created by aledermueller on 2015-01-14 12:15:14 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2017-01-14 13:05:54 +00:00 (in Redmine)


Hi,

i am using a HA-Setup like this:

object Endpoint "master1.domain" {
  host = "master1.domain"
}
object Endpoint "master2.domain" {
  host =  "master2.domain"
}
object Zone "master" {
  endpoints = [ "master1.domain", "master2.domain" ]
}

On each master i am using `icinga2 node update-config` to write the config which is sent from icinga2-agents. After the update-config icinga2 cannot be restarted, because master1 gets his own config from master2 and vice versa. This leads to a duplicated definition of zones, endpoints, hosts and services.

e.g. on master1 i have to remove

repository.d/zones/master.conf
repository.d/zones/master1.domain.conf
repository.d/endpoints/master2.domain.conf
repository.d/hosts/master1.domain.conf
repository.d/hosts/master1.domain/

Kind regards,
Achim


Parent Task: #13257

Relations:

@icinga-migration
Copy link
Member Author

icinga-migration commented Jan 14, 2015

Updated by aledermueller on 2015-01-14 12:22:53 +00:00

This is realted to #8211. If #8211 is fixed there should be a workaround with blacklists.

@icinga-migration
Copy link
Member Author

icinga-migration commented Apr 29, 2015

Updated by mfriedrich on 2015-04-29 16:27:04 +00:00

  • Tracker changed from Bug to Feature
  • Category set to Cluster

@icinga-migration
Copy link
Member Author

icinga-migration commented Apr 29, 2015

Updated by mfriedrich on 2015-04-29 16:50:25 +00:00

  • Relates set to 6196

@icinga-migration
Copy link
Member Author

icinga-migration commented Jul 24, 2015

Updated by mfriedrich on 2015-07-24 18:14:23 +00:00

  • Target Version set to Backlog

@icinga-migration
Copy link
Member Author

icinga-migration commented Sep 12, 2015

Updated by mfriedrich on 2015-09-12 09:05:21 +00:00

  • Relates set to 9927

@icinga-migration
Copy link
Member Author

icinga-migration commented Sep 12, 2015

Updated by mfriedrich on 2015-09-12 09:05:34 +00:00

This would be fairly easy if the objects are created through the API, and then synced to all other cluster nodes. See #9927 for details.

@icinga-migration
Copy link
Member Author

icinga-migration commented Sep 12, 2015

Updated by mfriedrich on 2015-09-12 09:05:45 +00:00

  • Relates set to 9332

@icinga-migration
Copy link
Member Author

icinga-migration commented Nov 18, 2016

Updated by mfriedrich on 2016-11-18 17:11:41 +00:00

  • Relates set to 13255

@icinga-migration
Copy link
Member Author

icinga-migration commented Nov 23, 2016

Updated by mfriedrich on 2016-11-23 14:53:30 +00:00

  • Target Version deleted Backlog

@icinga-migration
Copy link
Member Author

icinga-migration commented Jan 14, 2017

Updated by mfriedrich on 2017-01-14 13:05:54 +00:00

  • Parent Id set to 13257

@icinga-migration
Copy link
Member Author

icinga-migration commented Jan 14, 2017

Updated by mfriedrich on 2017-01-14 13:07:56 +00:00

  • Relates deleted 9332

@icinga-migration icinga-migration added enhancement area/distributed labels Jan 17, 2017
@dnsmichi
Copy link
Contributor

dnsmichi commented Feb 2, 2017

Closing since the entire mode will be removed with #4799.

@dnsmichi dnsmichi closed this as completed Feb 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/distributed enhancement
Projects
None yet
Development

No branches or pull requests

2 participants