Question:
I have a register task to test for the installation of a package:
|
1 2 3 4 5 |
tasks: - name: test for nginx command: dpkg -s nginx-common register: nginx_installed |
Every run it gets reported as a “change”:
|
1 2 3 |
TASK: [test for nginx] ******************************************************** changed: [vm1] |
I don’t regard this as a change… it was installed last run and is still installed this run. Yeah, not a biggy, just one of those untidy OCD type issues.
So am I doing it wrong? Is there some way to use register without it always being regarded as a change?
The [verbose] output is untidy, but the only way I’ve found to get the correct return code.
TASK: [test for nginx] ********************************************************
changed: [vm1] => {"changed": true, "cmd": ["dpkg", "-s", "nginx-common"], "delta": "0:00:00.010231", "end": "2014-05-30 12:16:40.604405", "rc": 0, "start": "2014-05-30 12:16:40.594174", "stderr": "", "stdout": "Package: nginx-common\nStatus: install ok
...
\nHomepage: http://nginx.net"}
Answer:
It’s described in official documentation here.
|
1 2 3 4 5 6 |
tasks: - name: test for nginx command: dpkg -s nginx-common register: nginx_installed changed_when: false |