Pedro Gomes

Seems there’s a bug (or a feature) somewhere in Ansible which doesn’t translate encrypted variables (but it works fine with vault files), so when you try to use them on a template it will fail with the error above.

To work around that, you could try setting a fact before hand which will decrypt the secure variable into a new variable.

set_fact:
pass_decoded: “{{ pass }}”

Use the new variable in the template:

Authorization: “Basic {{ (user + ‘:’ + pass_decoded)| b64encode }}”

--

--

Having issues to troubleshoot this error and finding the faulty host? Verbose mode won’t help you, neither will looking at your hosts.

One way to go at it, is to run ad-hoc commands, for instance we want to test the variable “ansible_host” which is (or should be) defined in host vars (we use it for templating):

ansible -i inventory all -m debug -a "var=hostvars[inventory_hostname].ansible_host"

Then you could get grep to filter out the matches like so:

ansible -i inventory all -m debug -a "var=hostvars[inventory_hostname].ansible_host" | grep -B1 "NOT DEFINED"

--

--

It’s only a matter of time when Ethereum becomes the number one crypto currency and all products are priced in gweis. In some measures Ethereum already beat Bitcoin. In others, it’s well underway to become #1.

It’s already doing 6x as many transactions as the Bitcoin network.

It has almost as many active wallets as Bitcoin.

The hype around NFT and DeFI will only keep growing ETH and leave Bitcoin well behind it’s stagnant growth.

Keep up with the flippening using https://flippening.org/

--

--