Hi,

Did the Hot dependencies still running on shinken 2.4

From arbiterlog it's semms ok

-bash-4.1$ grep srv1liv24 arbiterd.log
[1442099484] INFO: [Shinken] [Hot dependencies] Linked son : srv1liv24 and its father: srv1vmi20
[1442099485] EXTERNAL COMMAND: [1442099484] DEL_HOST_DEPENDENCY;srv1liv24;srv1vmi20
[1442101298] INFO: [Shinken] [Hot dependencies] Linked son : srv1liv24 and its father: srv1vmi20
[1442101299] EXTERNAL COMMAND: [1442101298] ADD_SIMPLE_HOST_DEPENDENCY;srv1liv24;srv1vmi20
[1442103139] INFO: [Shinken] [Hot dependencies] Linked son : srv1liv24 and its father: srv1vmi20
[1442103140] EXTERNAL COMMAND: [1442103139] DEL_HOST_DEPENDENCY;srv1liv24;srv1vmi20
[1442104905] INFO: [Shinken] [Hot dependencies] Linked son : srv1liv24 and its father: srv1vmi20
[1442104906] EXTERNAL COMMAND: [1442104904] ADD_SIMPLE_HOST_DEPENDENCY;srv1liv24;srv1vmi20


But by querying the livestatus , it'not ok, return srv1vmi18 (original config on the cfg file) instead of srv1vmi20.

-bash-4.1$ pynag livestatus --get hosts --columns "parents" --filter "host_name = srv1liv24"
parents
--------------------------------------------------------------------------------
[u'srv1vmi18']
----------1 objects matches search condition------------------------------------


MY config :

-bash-4.1$ grep modules arbiter-master.cfg
## Interesting modules:
modules PickleRetentionArbiter,VMWare_auto_linking


-bash-4.1$ cat VMWare_auto_linking.cfg
define module{
module_name VMWare_auto_linking
module_type hot_dependencies
mapping_file /tmp/vmware_mapping_file.json
mapping_command /var/lib/shinken/libexec/link_vmware_host_vm.py -x /var/lib/shinken/libexec/check_esx3.pl -V srv1vcp2 -u "*****" -p "****" -r 'lower|nofqdn' -o /tmp/vmware_mapping_file.json

mapping_command_interval 1800 ; optionnal
mapping_command_timeout 300 ; optionnal
}


Tia

Fred