On Tuesday, 12 May 2015 00:29:42 UTC+10, Marcus Franke wrote:
>
> if you are looking for problems with sudo you can login as your ansible
> user and issue "sudo -l". This will list all commands your ansible user is
> allowed to use.
>
The output of this command on the affected machine is as follows:
$ sudo -l
Matching Defaults entries for osmc on osmc:
env_reset, mail_badpass,
secure_path=/usr/local/sbin\:/usr/local/bin\:/usr/sbin\:/usr/bin\:/sbin\:/bin,
env_keep+=RPI_UPDATE_UNSUPPORTED, !secure_path
User osmc may run the following commands on osmc:
(root) NOPASSWD: ALL
To me, this indicates that after running sudo, the PATH should still
contain /sbin. My problems with Ansible's apt module seem to strongly
indicate that this is only not the case when Ansible is involved. Although
I appreciate that this is not easy to replicate on another machine, I still
feel that on the current balance of probabilities, this indicates an
Ansible bug. I'm happy to provide Ansible developers with SSH access to
this particular machine for further diagnosis if it's not possible to
suggest any other solutions at this time.
>From your sudo config files, %sudo group can fire all kind of commands, but
> needs a password. That's by intention?
>
This is a largely pre-configured system based off another distribution, so
it wouldn't surprise me if this definition is an unintended remnant from
the base distribution. The Ansible user is not part of the sudo group. so
I don't believe it should have any effect.
>
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/3b0da4ae-63fc-464d-9acd-67ab577b2ffe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
