Bug #17536

Return user-friendly message when working_dir not set

Added by Daniel Lobato Garcia 9 months ago. Updated 8 months ago.

Status:Closed
Priority:Normal
Assigned To:Daniel Lobato Garcia
Category:-
Target version:Foreman - Team Daniel - iteration 6
Difficulty: Pull request:https://github.com/theforeman/foreman_ansible/pull/61
Bugzilla link:

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 9 months 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 9 months ago

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

#2 Updated by Anonymous 9 months ago

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

#3 Updated by Daniel Lobato Garcia 8 months ago

  • Target version changed from Team Daniel - iteration 7 to Team Daniel - iteration 6

Also available in: Atom PDF