'Interactive authentication required' error even using 'become'

Archives Ansible Project
1

Hello everyone,

I’m using the following construction to start and stop wildfly service:

`

  • hosts: appserver
    remote_user: jenkins
    tasks:

  • name: Stop WildFly
    become: true
    become_user: wildfly
    become_method: sudo
    systemd:
    name: wildfly
    state: stopped

  • name: Start WildFly
    become: true
    become_user: wildfly
    become_method: sudo
    systemd:
    name: wildfly
    state: started

`

But in every time and after many combinations I’m still geting an error message:

Unable to stop service wildfly: Failed to stop wildfly.service: Interactive authentication required.

Similar construction (without systemcmd module) works fine:

`

  • name: Stop WildFly
    command: sudo systemctl stop wildfly
    become: true
    become_user: wildfly

`

And I don’t have any problems to switch to user wildfly using sudo, in the unix command line.

Do you have any ideas what could be wrong?

Ansible version: 2.3.2.0
Python version: 2.7.5
OS: RHEL 7.4

2

What if you use `service module just the sake for rather systemd… pls try below and see how it goes
it looks like a bug with systemd …

`

  • name: start WildFly service
    service:
    name: WildFly
    state: started
    enabled: True
    `
3

Still I got an error message:

fatal: [mydomain.com]: FAILED! => {
“changed”: false,
“failed”: true,
“invocation”: {
“module_args”: {
“daemon_reload”: false,
“enabled”: true,
“masked”: null,
“name”: “wildfly”,
“no_block”: false,
“state”: “stopped”,
“user”: false
}
},
“msg”: “Unable to enable service wildfly: Failed to execute operation: Interactive authentication required.\n”
}

W dniu poniedziałek, 30 października 2017 15:54:09 UTC+1 użytkownik Karn Kumar napisał:

4

I also tried to use become inside hosts section, but it also doesn’t help.

`

  • hosts: appserver
    remote_user: jenkins
    become: yes
    become_user: wildfly
    become_method: sudo
    tasks:

  • name: Stop WildFly
    become: true
    become_user: root
    become_method: sudo
    systemd:
    name: wildfly
    state: stopped

`

But in this case the following message appears:
sudo: a password is required

W dniu poniedziałek, 30 października 2017 12:07:48 UTC+1 użytkownik Dev napisał:

5

I do not think it is a systemd bug.

related to your first palybook in this mail-threadthe jenkins user or any other you use to connect to the system via ssh must have sudo capability (e.g: be in the wheel group)
and you need to pass the passwork with -K (or its moder equivalent)

6

Me too facing the same issue, privilege escalation is not working as expected. However, like you mentioned it works perfectly fine while using command/shell module. Please guide me if you got any solution.