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 #10980] icinga2 node update-config does not work well with indirect connected zones #3849

Closed
icinga-migration opened this issue Jan 18, 2016 · 11 comments

Comments

Projects
None yet
2 participants
@icinga-migration
Copy link
Member

commented Jan 18, 2016

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

Created by formorer on 2016-01-18 14:47:30 +00:00

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

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

Hi,

I have the following setup

master <- client <- client_of_client where "client_of_client" is connected via client to my master instance.
I do propagate configuration files from my clients to the master with icinga2 update-config.

Unfortunately the generated configuration files for the client_of_client are wrong:

cat zones/client_of_client.test.lan.conf
object Zone "client_of_client.test.lan" {
endpoints = [ "client.test.lan" ]
parent = "master.test.lan"
}

As you can see the parent is wrong. The hostcheck of the host is also wrong:

cat hosts/client_of_client.test.lan.conf :(
object Host "client_of_client.test.lan" {
import "satellite-host"
check_command = "cluster-zone"
}

The check_command is set to cluster-zone, which has the consequence that the hostcheck is always red. Dummy or something similar would work.


Parent Task: #13257

Relations:

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jan 29, 2016

Updated by mfriedrich on 2016-01-29 09:27:20 +00:00

  • Target Version set to Backlog
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Feb 10, 2016

Updated by DreiIT on 2016-02-10 11:49:41 +00:00

I can confirm the problem, reported by formorer.

The zones in my scenario are connected in following way:
master <- ssmon01.ifs.loc <- sscript01.ifs.loc

When icinga2 node update-config is run, the parents were not generated correctly:

Changes to be committed:

Adding host 'smon01.ifs.loc'
    check_command = "cluster-zone"
    import = [ "satellite-host" ]
Adding endpoint 'smon01.ifs.loc'
Adding zone 'smon01.ifs.loc'
    endpoints = [ "smon01.ifs.loc" ]
    parent = "mon3.3it.loc"
Adding host 'sscript01.ifs.loc'
    check_command = "cluster-zone"
    import = [ "satellite-host" ]
Adding endpoint 'sscript01.ifs.loc'
Adding zone 'sscript01.ifs.loc'
    endpoints = [ "sscript01.ifs.loc" ]
    parent = "mon3.3it.loc"

Also the check_command of the host 'sscript01.ifs.loc' should be 'dummy'.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Feb 10, 2016

Updated by DreiIT on 2016-02-10 15:00:31 +00:00

Correction: I had an error in my config, the check_command of 'sscript01.ifs.loc' is set right:

Adding host 'sscript01.ifs.loc'
    check_command = "dummy"
    import = [ "satellite-host" ]
    zone = "smon01.ifs.loc"
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Feb 22, 2016

Updated by vishnu on 2016-02-22 13:32:07 +00:00

I face the same issue too. As formorer said, I had to change zones/client-of-client.conf to change parent to client and hosts/client-of-client.conf to change check_command to "dummy" from "cluster-zone" to make host and services of client-of-client green in master's icingaweb2. Waiting for the fix.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Mar 18, 2016

Updated by mfriedrich on 2016-03-18 14:36:18 +00:00

That involves larger changes to how the configuration is pushed from clients to master (include satellites as "proxy"). This is currently not planned to be implemented soon.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Mar 18, 2016

Updated by mfriedrich on 2016-03-18 14:37:50 +00:00

  • Relates set to 9332
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Nov 18, 2016

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

  • Relates set to 13255
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Nov 23, 2016

Updated by mfriedrich on 2016-11-23 14:57:26 +00:00

  • Target Version deleted Backlog
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jan 14, 2017

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

  • Parent Id set to 13257
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jan 14, 2017

Updated by mfriedrich on 2017-01-14 13:08:03 +00:00

  • Relates deleted 9332
@dnsmichi

This comment has been minimized.

Copy link
Member

commented Feb 2, 2017

@dnsmichi dnsmichi closed this Feb 2, 2017

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.