Open log1-c opened 6 months ago
Looks like this is more of a general problem (with services being named the same at multiple locations?) We recently switched some service from Director-based service sets to Icinga DSL in the config files.
Now the modify of said services show that they still have the origin of the service set,
Current Behavior
Example, if set is assigned via dictonary key&value
Service sentienlone_threats is in two service sets.
Set _windows-agent-managedsentinelone: has the following assign statement:
assign where host.vars.os_family == "windows" && !(host.vars.tags.ic_service_wts == "yes" || host.vars.tags.ic_service_wts == "true") && ! host.vars.appliance && host.vars.os_layer == "managed"
Set _ic_service_vdsentinelone: has the following assign statement
assign where host.vars.os_family == "windows" && host.vars.tags.ic_service_vd_sentinelone == "true"
As can be seen, the service differ in small details. The assignment itself works. The services are shown and executed as configured
Service of set_windows-agent-managedsentinelone:![image](https://github.com/Icinga/icingaweb2-module-director/assets/24474580/19a8f5f9-b007-4a19-a4d2-ca0b7f833038)
Service of set _ic_service_vdsentinelone:![image](https://github.com/Icinga/icingaweb2-module-director/assets/24474580/4300996f-93c7-4cae-b901-bb4f8d58ef5a)
But when clicking "Modify" on the service with origin _ic_service_vdsentinelone the Director shows _windows-agent-managedsentinelone as source set and is even showing the wrong values![image](https://github.com/Icinga/icingaweb2-module-director/assets/24474580/5e44c4c1-9d61-4660-bd6d-8c0f77f34486)
Seems to be related to: https://github.com/Icinga/icingaweb2-module-director/issues/2582
Your Environment
icinga2 --version
): 2.14.0