Project

General

Profile

Bug #23279

when running ansible job become is not working

Added by Lukas Pramuk about 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

effective user (both real or nonsense) is ignored and root is always used.
While for SSH provider this works.

Associated revisions

Revision 7afda4b7 (diff)
Added by Daniel Lobato García almost 4 years ago

Fixes #23279 - Enable 'ansible_become' to work with REX (#184)

Since 'supports_effective_user?' was not implemented in the Ansible
provider, it was returning 'false'. That means that every time you set
an effective user in the Job Invocation form, it gets saved as nil (see
foreman_remote_execution/app/models/template_invocation#
set_effective_user)

History

#1 Updated by Lukas Pramuk about 4 years ago

foreman-1.18.0-0.develop.201804091403git41fe8c6.el7.noarch
katello-3.7.0-1.nightly.el7.noarch
tfm-rubygem-foreman_ansible-2.0.4-1.fm1_18.el7.noarch > updated to foreman_ansible (2.1.0)
tfm-rubygem-foreman_ansible_core-2.0.2-1.fm1_18.el7.noarch
rubygem-smart_proxy_ansible-2.0.2-3.fm1_18.el7.noarch
ansible-2.5.0-2.el7.noarch

#2 Updated by Lukas Pramuk almost 4 years ago

  • Bugzilla link set to 1589819

#3 Updated by Marek Hulán almost 4 years ago

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

#4 Updated by Marek Hulán almost 4 years ago

  • Target version set to foreman-ansible 2.2.2

#5 Updated by Anonymous almost 4 years ago

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

Also available in: Atom PDF