Missing lines in <var>.stdout_lines?

Archives Ansible Project
1

I have a task that installs nvm and node. When installing node (i.e. nvm install v0.12.2), Ansible seems to think the machine state has been changed, even if that version of Node is already installed. When run from the command line when the version is already there, I get this:

$ nvm install v0.12.2
v0.12.2 is already installed.
Now using node v0.12.2 (npm v2.7.4)

I added the following to the task:

register: node_installed
changed_when: “‘is already installed’ is not in node_installed.stdout”

It never picked up and continued to reflect a change, perhaps because there are multiple lines in the output. However, when I debug: node_installed.stdout_lines I still only get the second line.

What am I missing?

2

It looks like you need to inspect node_installed.stderr instead of stdout. The string you are looking for seems to go there instead.

ok: [localhost] => {
“changed”: false,
“foo”: {
“_ansible_no_log”: false,
“changed”: true,
“cmd”: “. /Users/matt/.nvm/nvm.sh && nvm install v0.12.2”,
“delta”: “0:00:04.243197”,
“end”: “2015-10-16 09:41:08.582763”,
“rc”: 0,
“start”: “2015-10-16 09:41:04.339566”,
“stderr”: “v0.12.2 is already installed.”,
“stdout”: “Now using node v0.12.2 (npm v2.7.4)”,
“stdout_lines”: [
“Now using node v0.12.2 (npm v2.7.4)”
],
“warnings”:
}
}

3

Thanks, Matt. You beat me to it.

I didn’t expect that to generate an error, but after posting (unfortunately) I figured I should just inspect the whole variable and I found what you found. Punitive head slap for me.

I appreciate the assist.