[dev.icinga.com #11793] node setup: Add a note for --endpoint syntax for client-master connection

[icinga-migration]

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

Created by evgeni on 2016-05-16 13:55:50 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2016-05-25 08:30:03 +00:00)
Target Version: 2.5.0
Last Update: 2016-06-16 08:11:38 +00:00 (in Redmine)

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

---

When one runs

icinga2 node setup --ticket $TICKET --endpoint $MASTER --zone $HOSTNAME --master_host $MASTER --trustedcert /etc/icinga2/pki/trusted-master.crt

icinga will generate the following entry in zones.conf:

object Endpoint "$MASTER" {
}

This is not sufficient and i2 will not connect to the master. When one runs either

icinga2 node wizard

or

icinga2 node setup --ticket $TICKET --endpoint $MASTER,$MASTER,5665 --zone $HOSTNAME --master_host $MASTER --trustedcert /etc/icinga2/pki/trusted-master.crt

a correct entry is created and the connection works:

object Endpoint "$MASTER" {
        host = "$MASTER"
        port = "5665"
}

Changesets

2016-05-25 08:24:18 +00:00 by mfriedrich 2356ec0

node setup: Add a note for --endpoint syntax for client-master connection

fixes #11793

[icinga-migration]

Updated by gbeutner on 2016-05-17 06:25:12 +00:00

• Status changed from New to Feedback
• Assigned to set to evgeni

As far as I can see this isn't a bug. There are scenarios where the satellite shouldn't (or, actually, can't - thanks to firewall rules) connect to the master. As long as the master has host/port set for the satellite Endpoint things should work just fine.

Or am I missing something here? :)

[icinga-migration]

Updated by gbeutner on 2016-05-24 06:33:10 +00:00

• Status changed from Feedback to Rejected
• Assigned to deleted evgeni

[icinga-migration]

Updated by evgeni on 2016-05-24 06:47:10 +00:00

I thought passing --endpoint does exactly that: tells icinga to connect to a remote instance (and thus expect firewalls to work).
At least that's how I read http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/object-types#objecttype-endpoint
The initial command line was even taken from the docs: http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/icinga2-client#icinga2-client-installation-client-setup-linux-manual

[icinga-migration]

Updated by gbeutner on 2016-05-24 07:06:49 +00:00

• Status changed from Rejected to Assigned
• Assigned to set to evgeni

[icinga-migration]

Updated by mfriedrich on 2016-05-25 08:12:23 +00:00

Nothing in the docs where I would get an idea like that. I'll add a note on modifying the --endpoint parameter to allow the client connecting to the parent zone accordingly.

[icinga-migration]

Updated by mfriedrich on 2016-05-25 08:25:27 +00:00

• Subject changed from 'icinga2 node setup' creates broken Endpoint in zones.conf to node setup: Add a note for --endpoint syntax for client-master connection
• Assigned to changed from evgeni to mfriedrich
• Target Version set to 307

[icinga-migration]

Updated by mfriedrich on 2016-05-25 08:25:53 +00:00

• Category changed from API to Documentation

[icinga-migration]

Updated by mfriedrich on 2016-05-25 08:30:03 +00:00

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

Applied in changeset 2356ec0.

[icinga-migration]

Updated by gbeutner on 2016-06-16 08:11:38 +00:00

• Target Version changed from 307 to 2.5.0