Project

General

Profile

Bug #17150

Ansible Plugin uses the foreman user as ssh user to execute playbooks

Added by Daniel Kuffner over 2 years ago. Updated 10 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Difficulty:
Triaged:
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Ansible Plugin uses the 'foreman' user to open a ssh connection ( foreman@myhost ). I tried to configure the ssh user via global/host parameters in the foreman web ui - without luck.

I tried all to me know ansible variables:
- remote_user
- ansible_user
- ansible_ssh_user

How is it possible to configure the ssh user?

How is it possible to configure the ssh user in the ansible plugin?


Related issues

Related to Foreman - Feature #17527: As a developer, I want to have facets easily applicable to both hosts and host groups.Closed

Associated revisions

Revision a818cfbd (diff)
Added by Tomer Brisker over 2 years ago

Fixes #17150 - Allow setting some ansible connection parameters

This currently allows setting the ansible_user, ansible_port and
ansible_ssh_pass for all hosts. There is a default setting which can
also be overriden by using host or hostgroup parameters with the same
name.

History

#1 Updated by Daniel Kuffner over 2 years ago

Versions:
ansible 2.1.2.0

rpm -qa | grep foreman
foreman-release-scl-3-1.el7.noarch
foreman-1.13.1-1.el7.noarch
tfm-rubygem-foreman_setup-5.0.0-1.fm1_13.el7.noarch
tfm-rubygem-foreman-tasks-0.8.2-1.fm1_13.el7.noarch
foreman-release-1.13.1-1.el7.noarch
foreman-selinux-1.13.1-1.el7.noarch
foreman-installer-1.13.1-1.el7.noarch
foreman-debug-1.13.1-1.el7.noarch
foreman-postgresql-1.13.1-1.el7.noarch
foreman-proxy-1.13.1-1.el7.noarch
tfm-rubygem-hammer_cli_foreman-0.8.0-1.el7.noarch
tfm-rubygem-foreman_ansible_core-0.0.1-2.fm1_13.el7.noarch
tfm-rubygem-foreman_ansible-1.2.1-1.fm1_13.el7.noarch
foreman-cli-1.13.1-1.el7.noarch
tfm-rubygem-foreman-tasks-core-0.1.1-1.fm1_13.el7.noarch

#2 Updated by Daniel Lobato Garcia over 2 years ago

Terrifyingly, I forgot to do this - no way to configure it as of now. I'll do my best to release a new version that allows that.

#3 Updated by Daniel Lobato Garcia over 2 years ago

The smart proxy plugin doesn't allow setting the user either

#4 Updated by Tomer Brisker over 2 years ago

  • Status changed from New to Assigned
  • Assignee set to Tomer Brisker

#5 Updated by Shimon Shtein over 2 years ago

  • Blocked by Feature #17527: As a developer, I want to have facets easily applicable to both hosts and host groups. added

#6 Updated by Tomer Brisker over 2 years ago

  • Blocked by deleted (Feature #17527: As a developer, I want to have facets easily applicable to both hosts and host groups.)

#7 Updated by Tomer Brisker over 2 years ago

  • Related to Feature #17527: As a developer, I want to have facets easily applicable to both hosts and host groups. added

#8 Updated by The Foreman Bot over 2 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_ansible/pull/60 added

#9 Updated by Anonymous over 2 years ago

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

#10 Updated by Daniel Lobato Garcia over 2 years ago

  • Target version set to 1.4.3

Also available in: Atom PDF