[dev.icinga.com #10733] slaves can't modify objects (ack, comment, downtime)

[icinga-migration]

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

Created by penyilas on 2015-11-26 17:18:47 +00:00

Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2016-11-09 14:52:21 +00:00 (in Redmine)

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

---

Hi,

I've a 2 master 2 satellite configuration
I'm running icinga-web2 on satellites (because they've more resources, than the masters)

On 2.3.11, it worked perfectly, but now, I can't ack a problem, schedule downtime, etc, because:

warning/ApiListener: Discarding 'config update object' message from 'slave1'

If I install an icinga-web2 into master, it's working again, but I'd like to avoid it.

Can you add some exceptions into here?
https://github.com/Icinga/icinga2/blob/master/lib/remote/apilistener-configsync.cpp#L91

Regards,
Peter Nyilas

---

Relations:

• relates #10505
• relates #10733

[icinga-migration]

Updated by mfriedrich on 2015-11-26 17:35:04 +00:00

Add accept_config = true to your slaves' ApiListener config

[icinga-migration]

Updated by penyilas on 2015-11-26 17:59:00 +00:00

dnsmichi wrote:

Add accept_config = true to your slaves' ApiListener config
Of course, it's enabled (both of masters, both of satellites)

Here's again, it looks, i wasn't clear...
So I've run extenal command on slave1 (one of satellite)
[2015-11-26 17:08:17 +0000] information/ExternalCommandListener: Executing external command: [1448557697] ADD_SVC_COMMENT;slave1;cluster;1;Icinga 2 Admin;test

On master1 this "config-update" was discarded:
[2015-11-26 17:08:18 +0000] warning/ApiListener: Discarding 'config update object' message from 'slave1'.

In this case, this comment will not persisted into innodb, because master was discarded this message

[icinga-migration]

Updated by mfriedrich on 2015-11-26 18:01:39 +00:00

That wasn't supported in older versions either.

[icinga-migration]

Updated by penyilas on 2015-11-26 18:02:29 +00:00

dnsmichi wrote:

That wasn't supported in older versions either.

It worked before 2.4.0

[icinga-migration]

Updated by mfriedrich on 2016-01-22 15:17:50 +00:00

• Target Version set to Backlog

[icinga-migration]

Updated by tobiasvdk on 2016-02-16 11:02:51 +00:00

I also get the error message, but ack's are "synced". Nevertheless icingaweb2 does'nt show all information, see #10505

But e.g. downtimes don't work.

[icinga-migration]

Updated by tobiasvdk on 2016-02-16 11:02:57 +00:00

• Relates set to 10505

[icinga-migration]

Updated by mfriedrich on 2016-03-18 15:30:52 +00:00

• Parent Id set to 11313

[icinga-migration]

Updated by mfriedrich on 2016-03-29 08:46:32 +00:00

• Priority changed from Normal to High

[icinga-migration]

Updated by mfriedrich on 2016-03-29 10:08:43 +00:00

• Relates set to 11227

[icinga-migration]

Updated by mfriedrich on 2016-11-09 14:52:21 +00:00

• Parent Id deleted 11313

[xenuser]

I can confirm this bug with Icinga 2.6.1. It would be great to see if this issue could be fixed any time soon. In enterprise environments, it could be the case that e.g. Icinga clients schedule a downtime for themselves at their responsible satellite (e.g. before a reboot). In this case, we can not allow the clients to talk to the master directly, which is why it would be great to see that creating downtimes on satellites actually works again.

[dnsmichi]

That behaviour changed in 2.4 and we haven't touched it ever since. It has been discussed a while ago in #4969 although it is unclear whether we change it back, or not. For the time being, this isn't really a bug anymore but a current behaviour which might need changes. We don't have any plans or time currently to look further into it, but you're welcome to suggest possible design changes (as a matter of security) or send a PR even :)

[dombyy]

I have same issues with my nodes after upgrading from 2.4.x to 2.6.1.

"warning/ApiListener: Discarding 'config update object' message from"

Of course accept_config is true.

[jar361]

I have the same issues with my nodes on version 2.6.2-1

[xenuser]

@dnsmichi Thanks for the fast reply. I will contact you directly during the Icinga Camp then, I guess :) Would be great to hear some more thoughts regarding the design decisions and how a possible change could look like.

[dombyy]

I just compiled from the source, and working fine again. Previously I tried via DEB packages.

[dnsmichi]

@dombyy Uhm I doubt that compiling from source changes anything regarding the requested behaviour. What exactly did you test?

[dombyy]

I did not do test, i just upgraded from 2.4.x to 2.6.1, and nodes stopped sync the configs. Then I grabbed the source, compiled everything, and its working again, with the 'Discard config' messages.

[gunnarbeutner]

There are no plans to support this.