-
Incident report
-
Resolution: Won't fix
-
Major
-
None
-
2.0.0
Ok, this one is a bit strange but I can easily reproduce it....
I'm using a simple perl script to add new host to a DM setup. It works flavelessly on one host in the DM setup but not on the other node
(In my example Fellerstrasse is node1 (master) and Bundesrain is node2 (child))
TEEGFE66 @ Fellerstrasse : failed -> No permissions to referred object or it does not exist!
BXEGFE03 @ Fellerstrasse : failed -> No permissions to referred object or it does not exist!
EREGFE101 @ Fellerstrasse : failed -> No permissions to referred object or it does not exist!
FAEGFE02 @ Fellerstrasse : failed -> No permissions to referred object or it does not exist!
FAEGFE101 @ Fellerstrasse : failed -> No permissions to referred object or it does not exist!
FAEGFE118 @ Fellerstrasse : failed -> No permissions to referred object or it does not exist!
FAEGTB101 @ Bundesrain : failed -> Host with the same name "FAEGTB101" already exists.
TEEGFE65 @ Fellerstrasse : failed -> No permissions to referred object or it does not exist!
TKEGFE40 @ Fellerstrasse : failed -> No permissions to referred object or it does not exist!
Result is basically that it works on node 2 but not on node 1.
The strange thing now is that (!!) when I add the admin user on node Fellerstrasse into the "Enable debug mode" group and open the debug console it then works fine on node 1 but no longer on node 2
TEEGFE66 @ Fellerstrasse : success (hostid: 100100000010091)
BXEGFE03 @ Fellerstrasse : success (hostid: 100100000010092)
EREGFE101 @ Fellerstrasse : success (hostid: 100100000010093)
FAEGFE02 @ Fellerstrasse : success (hostid: 100100000010094)
FAEGFE101 @ Fellerstrasse : success (hostid: 100100000010095)
FAEGFE118 @ Fellerstrasse : success (hostid: 100100000010096)
FAEGTB101 @ Bundesrain : failed -> No permissions to referred object or it does not exist!
TEEGFE65 @ Fellerstrasse : success (hostid: 100100000010097)
TKEGFE40 @ Fellerstrasse : success (hostid: 100100000010098)
So now it works fine with node 1 but no longer with node 2 !!
I can swap this behavior easiley by adding/removing the user into the nodes "enabled debug user" group.