Bug #17536

Return user-friendly message when working_dir not set

Added by Daniel Lobato Garcia over 1 year ago. Updated 7 days ago.

Status:Closed
Priority:Normal
Assignee:Daniel Lobato Garcia
Category:-
Target version:1.4.3
Difficulty: Team Backlog:
Triaged: Fixed in Releases:
Bugzilla link: Found in Releases:
Pull request:https://github.com/theforeman/foreman_ansible/pull/61

Description

Currently if the user is lacking the 'ansible_working_dir' key in their proxy settings, the task output will not be very helpful when the user tries to debug what happened. It'll just say `no method error .present? called on nil' or similar. Instead, the AnsibleCore playbook runner needs to be aware of this situation and provide a friendlier error message.

Associated revisions

Revision 4bee3b4f
Added by Daniel Lobato García over 1 year ago

Fixes #17536 - Return user-friendly message when working_dir not set

Currently if the user is lacking the 'ansible_working_dir' key in their
proxy settings, the task output will not be very helpful when the user
tries to debug what happened. It'll just say `no method error .present?
called on nil' or similar. Instead, the AnsibleCore playbook runner
needs to be aware of this situation and provide a friendlier error
message.

History

#1 Updated by The Foreman Bot over 1 year ago

  • Status changed from New to Ready For Testing
  • Assignee set to Daniel Lobato Garcia
  • Pull request https://github.com/theforeman/foreman_ansible/pull/61 added

#2 Updated by Anonymous over 1 year ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#3 Updated by Daniel Lobato Garcia over 1 year ago

  • Target version changed from 1.15.2 to 1.4.3

Also available in: Atom PDF