As a matter of fact they all do start with zero. I understand your
explanation, but one thing bothers me about it: when this playbook ran
earlier on four machines, those site numbers all started with 0 and we had
no problem, and on this run all 6 started with 0 and we only had the
problem on 4
Without knowing what those 4 digit identifiers are, it would be hard to
say. Do they start with the number 0? If so, they may have been treated
as oct instead of int, and then the int was placed in that file.
Such as 0456 being the same as 302, where 0456 was oct, and 302 is the int
value.
On
I have run a playbook that updates an app of ours on numerous customer
VM's. This playbook has run fine many times, but today when I ran it to
update 6 servers, one of my variables was not properly put into the target
files on 4 of the 6 VM's. More specifically, this variable is a four digit
