diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2017-11-14 20:01:36 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-11-14 20:01:36 -0800 |
| commit | c5afbd8a7643f323f02c3bb1c04cf7f40444995c (patch) | |
| tree | e8c1dd78429c125e338cba997974303193ec31aa /playbooks/byo/openshift-etcd/embedded2external.yml | |
| parent | dbbfefbdeb6336105e415cb478193800e11a3134 (diff) | |
| parent | e31dd8e318bc6bc889b471a57e4559376591a9e5 (diff) | |
| download | openshift-c5afbd8a7643f323f02c3bb1c04cf7f40444995c.tar.gz openshift-c5afbd8a7643f323f02c3bb1c04cf7f40444995c.tar.bz2 openshift-c5afbd8a7643f323f02c3bb1c04cf7f40444995c.tar.xz openshift-c5afbd8a7643f323f02c3bb1c04cf7f40444995c.zip | |
Merge pull request #6091 from sosiouxme/20171110-ini-parse-failure
Automatic merge from submit-queue.
ansible.cfg: error when inventory does not parse
As of Ansible 2.4 this option exists:
https://github.com/ansible/ansible/issues/15035#issuecomment-329672168
The kind of error you get later when this is your real problem tends to be *very* confusing. Much better to just fail right away.
I cannot think of any scenario in which it would be preferable to proceed when inventory parsing fails.
Diffstat (limited to 'playbooks/byo/openshift-etcd/embedded2external.yml')
0 files changed, 0 insertions, 0 deletions