Hello everyone,
we’re currently using CEE2.1.0p32,RHEL8 and are having quite a problem with the result of the rule “Check State of BI Aggregation”.
Out of circumstances, we’re forced to use the BI-status of host aggregations as host check command. Not beautiful, but it is, what it is. The problem occurs here now.
We set up brand new servers (bc jump vom 1.5 to >2.X) and are experiencing quite a few problems to activate change. The satellites with a lot of hosts always tells us, that there are new change to discover, so we can’t activate the current changes.
Problem here, our sites have all disabled wato configuration, so there can’t be any change at all at the sites and we know (we checked), that there is no RestAPI connection from outside.
After a little bit of engineering i found out, that the file “~/lib/python3/cmk/gui/plugins/openapi/restful_objects/decorators.py” has in line 824 the following condition for counting up “imaginary changes” (or “changes could be” counter):
if self.method != "get" and response.status_code < 300 and self.update_config_generation:
The problem is, that the rule “Check State of BI Aggregation” uses POST-Requests to ask the status of the BI, which response with a “200” OK status. We have around >1000 hosts on one of our sites (and counting) and are forced to check the state each minute, so there are a lot of POST-Requests regarding their host-bi-aggregations.
That’s the reason, we can’t activate any changes at this site, because it thinks, that there happened some kind of changes even though, we just ask for a status.
Are we really the only one with this problem or are we the only one using it at this scale?
I can barely imagine that.
Hope someone can help me or give me a proper solution to fixing this problem beside commenting-out the specific line for update the config file id.
Regards Kruzgoth
