I think I found the issue. The issue is that when I run the installer even though I provide an answer file like the directions say the installer still prompts when I run it locally. I thought it used the answer file to just run the installer without prompts. I guess not.
On Tuesday, January 12, 2016 at 11:06:05 AM UTC-5, Mark Constant wrote: > > I have a playbook where I have to run a bunch of commands as sudo. So at > the beginning of the playbook I put become: yes. > The issue is there is one command running a shell script where the shell > script can't be run as super user. Almost like I have to deescalate > privileges. > If I just run the playbook I get the error from the .sh installer that you > can't run as root. > Under the name: Install Product I have tried everything to switch users to > a non root user but the playbook basically hangs. I can't tell where the > issue is. Nothing happens. > > I have tried > Name: Install Software > become: no > > Also have tried > Name: Install Software > become: yes > become_user: rhapuser > become_method: su > > But no matter what I do it just stalls at TASK: Install Software > > Is there a way to basically remove root privileges for just one command or > figure out why it is not running? > -- 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/620fae9c-65aa-46a6-8e24-2552b2a7a19e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
