Remove 'ignore_errors: true' in favor of 'failed_when: false'
This change removes the use of 'ignore_errors: true' because it causes deployers to see red output and a stacktrace, which traditionally means something is broken, even when the failure is known to have a fall back option or be intentional. This conversion will provide a generally cleaner interface. It should be noted that the 'failed' filter will still function normally. Tasks with the 'failed_when: false' option will still be marked as 'failed' in any registered variable. This change simply makes the output look cleaner. Change-Id: I460b4eb12c30d66769f3093a451dc39c77150ea3 Closes-Bug: #1633438 Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
This commit is contained in:
parent
ac801399f5
commit
696056db67
@ -53,7 +53,7 @@
|
|||||||
state: "present"
|
state: "present"
|
||||||
register: add_keys
|
register: add_keys
|
||||||
until: add_keys|success
|
until: add_keys|success
|
||||||
ignore_errors: True
|
failed_when: false
|
||||||
retries: 5
|
retries: 5
|
||||||
delay: 2
|
delay: 2
|
||||||
with_items: "{{ haproxy_gpg_keys }}"
|
with_items: "{{ haproxy_gpg_keys }}"
|
||||||
|
Loading…
x
Reference in New Issue
Block a user