CMK version: 2.5.0p7 - Multisite setup
OS version: Debian13
I’m actually not sure if this is expected behaviour but we’ve recently come across unexpected behaviour when configuring and applying a new Auxiliary tag.
Our intent was to use an aux tag in a Notification Rule to create notifications for systems carrying this aux-tag.
We’ve configured a new aux-tag and in the same config-session added it to several (normal) tags which were already applied to several hosts.
After activating the changes, creating and testing the Notification-Rule we found that despite the fact that it has been configured via the web-interface the aux-tag had not been applied to the hosts carrying the normal tags that are connected to the new aux-tag.
To fix this we simply needed to once again touch the tag-group, uncheck and recheck the box to apply the aux-tag to the respective tag-choices and activate the changes on all sites once again.
No Warning is displayed when creating an aux-tag - and it is not even possible to activate changes when creating a new aux-tag without using it.
I suppose this could be a problem with the order of aux-tags and normal tags when the new config is applied on the sites causing this to happen.
I’d be happy if someone can check and confirm that this is actually unexpected - and unwanted behaviour.