Exacly!
I've created a new user (usertest) on the Control Node and tried to connect
to the managed node, with the same conditions as before (ansible user with
no priv. escalation nor ansible_user var defined).
Result --> SSH raised an authentication error =)
Thank you Vladimir.
El lunes, 7 de
Anyone can help me
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web
On Mon, Oct 7, 2019, at 4:19 PM, Troy Cosson wrote:
> I'm trying to get a Red Hat server (RHEL7) to join a Windows Active
> Directory domain and I can't seem to get the expect command to send a
> password.
>
> The playbook asks for the username and password and should then put the
> username
On Mon, 7 Oct 2019 12:42:24 -0700 (PDT)
Vicente Domínguez wrote:
> Let's imagine that I don't have ANSIBLE user on the managed host, as
> follows:
> -->Control Node: ANSIBLE - ROOT
> -->Managed Host: SSHUSER - ROOT
> [...]
> If ANSIBLE is my default "ansible_user" and It establishes a SSH
I'm trying to get a Red Hat server (RHEL7) to join a Windows Active
Directory domain and I can't seem to get the expect command to send a
password.
The playbook asks for the username and password and should then put the
username at the end of the adcl command
adcli join example.com -U
Thank you Vladimir for your quick and useful answer!
I've understood the basis now, but.. it raises the question below:
Let's imagine that I don't have ANSIBLE user on the managed host, as
follows:
-->Control Node: ANSIBLE - ROOT
-->Managed Host: SSHUSER - ROOT
Taking into account that I am
On Mon, 7 Oct 2019 10:57:49 -0700 (PDT)
Vicente Domínguez wrote:
> I have 2 nodes with the following users:
> Control Node: ANSIBLE - ROOT
> Managed Host: ANSIBLE - SSHUSER - ROOT
> [...]
> So my question is, why is the user ANSIBLE (managed host's user) the one
> executing the task in
Hello everybody,
Regarding the understanding of how the REMOTE_USER works in managed hosts..
I've created a playbook which executes the command ID, with the aim of
knowing who is the user executing the action in the managed host.
[image: Captura2.PNG]
I have 2 nodes with the
Thank you so much to both of you :)
The fact is that I started doubting about this basic concept when I tried
to create a new USER4 in the managed host, and I faced several troubles to
connect as USER4 (remote_user).
Despite of exchanging the SSH Pub Keys I still facing the PERMISSION DENIED
On 07.10.2019 18:00, Vicente Domínguez wrote:
I am sure that this is probably a silly question, but It's the basis
for
the preparation for Ansible certification exam. I have troubles with
the
understanding of the Ansible remote_user.
Let's imagine that you have a control node and a managed
On Mon, 7 Oct 2019 09:00:51 -0700 (PDT)
Vicente Domínguez wrote:
> Control node --> ROOT, User1 , User2, User3
> Managed Host --> ROOT, User3
>
> So, if you are logged as ROOT in the control node, and you execute a
> playbook to perform some action in the managed host, and you use the key
>
On 07.10.2019 15:42, Revanth Mallikarjun wrote:
I'm not able to see the logs for few of the tasks,
Awx job will get failed and it doesn't show any logs . For example,
if the task was to install a package using yum .
It just stops there and get failed.I have tried to increase the logs
I don't see anything related to Ansible in your question?
If there is - please share that and we can have a look.
Dick
On Mon, 7 Oct 2019 at 11:29, Mohtashim S wrote:
>
> Below code works and helps fetch username and password from Jenkins
> credentials in a piepeline.
>
>
>
I am sure that this is probably a silly question, but It's the basis for
the preparation for Ansible certification exam. I have troubles with the
understanding of the Ansible remote_user.
Let's imagine that you have a control node and a managed host to perform
some action, the users in both
Hi Jon,
The link you provided has worked wonders, I have found 'win_feature' module
does more than I need.
--
Thank you.
Stephen.
On Friday, 4 October 2019 21:38:16 UTC+1, J Hawkesworth wrote:
>
> Well to get rid the warning, remove the "{{ and }} " from your 'when'
> clause. The 'when'
I'm not able to see the logs for few of the tasks,
Awx job will get failed and it doesn't show any logs . For example, if the
task was to install a package using yum .
It just stops there and get failed.I have tried to increase the logs verbose
as well.Did not display any logs.
--
You
Hi All,
Thanks for your time and efforts to help me out with the issue. I
understood the mistak. I missed out making changes in the config file as
described in below link
https://docs.ansible.com/ansible/latest/user_guide/playbooks_variables.html#caching-facts
TA
On Fri, Oct 4, 2019 at
Below code works and helps fetch username and password from Jenkins
credentials in a piepeline.
withCredentials([usernamePassword(credentialsId: 'mysql_creds',
passwordVariable: 'sqlpassword', usernameVariable: 'sqlusername')])
{
creds = "\nUsername: ${sqlusername}\nPassword:
I am trying to create a few AD groups from a remote RHEL development
machine. However, when my playbook reaches this task:
- name: "AD | Create access group"
win_domain_group:
name: "GLS_{{ servername }}_access"
category: security
display_name: "GLS_{{ servername
19 matches
Mail list logo
