Actions
Bug #32030
closed
Using localhost in a playbook causes a crash
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:
Description
Using any of the available Ansible techniques to run a local task in a Foreman-templated playbook (e.g. `delegate_to: locahlhost`, `connection: local` etc) causes a crash in the Foreman logging plugin:
2021-03-07T10:03:11 [E] error while dispatching request to runner 9be89c5e-7565-4824-ab5a-1d704d7315de:NoMethodError undefined method `add_output' for nil:NilClass:
/usr/share/gems/gems/foreman-tasks-core-0.3.4/lib/foreman_tasks_core/runner/parent.rb:47:in `publish_data_for'
/usr/share/gems/bundler/gems/foreman_ansible-0d49745fab69/lib/foreman_ansible_core/runner/ansible_runner.rb:66:in `handle_host_event'
Updated by The Foreman Bot about 3 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman_ansible/pull/391 added
Updated by Ondřej Ezr about 3 years ago
- Related to Bug #32188: Verbose log outputs for Ansible jobs are reported to all Hosts present on the Job. added
Updated by The Foreman Bot about 3 years ago
- Assignee set to Ondřej Ezr
- Pull request https://github.com/theforeman/foreman_ansible/pull/398 added
Updated by The Foreman Bot over 2 years ago
- Pull request https://github.com/theforeman/smart_proxy_ansible/pull/55 added
Updated by The Foreman Bot almost 2 years ago
- Fixed in Releases smart_proxy_ansible-3.4.0 added
Updated by Anonymous almost 2 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset smart_proxy_ansible|6398f95f52c53adc66f9d5bc23a26df71adff93c.
Actions