FOUND IT: if you run local_action wait_for with sudo: true, make sure your *local* user doesn't require a sudo password either by editing /etc/sudoers locally (eg mathias ALL=(ALL) NOPASSWD: ALL)!
Mathias On Monday, 2 December 2013 19:23:29 UTC, Mathias Bogaert wrote: > > Hi Michael, > > The system has SSH keys installed, and never requires any passwords. > > The command line options are ansible-playbook -i hosts --extra-vars > "accelerate=true" site.yml. > I'll debug it a bit further, but this definitely worked using Ansible 1.3. > > Cheers, > Mathias > > On Sunday, 1 December 2013 14:22:06 UTC, Michael DeHaan wrote: >> >> It just looks like the system didn't take a sudo password before, you >> rebooted it, and now it needs a sudo password to me. >> >> You didn't show any of the command line options you used to execute >> Ansible with though, so it's hard to say with incomplete information. >> >> Don't think that's a 1.3/1.4 thing but assumptions that --sudo-user meant >> sudo at one point *did* change, though I believe that was way back in 1.2. >> >> You'll probably have to debug a bit further to see what's exactly going >> on. >> >> Public service announcement: there is no SLA for asking for free support >> here, and we're likely going to be always prioritizing larger issues >> affecting more users than an isolated report. If you require a SLA, our >> support and services guys are *excellent*, and you get an AWX license >> included with that. Bonus! >> >> --Michael >> >> >> >> >> >> >> >> >> >> >> On Thu, Nov 28, 2013 at 6:26 PM, Mathias Bogaert <[email protected]>wrote: >> >>> Ping? >>> >>> >>> On Tuesday, 26 November 2013 21:50:17 UTC, Mathias Bogaert wrote: >>>> >>>> Hi James, >>>> >>>> The playbook is available here: >>>> >>>> https://github.com/analytically/hadoop-ansible >>>> >>>> The roles that has the reboot here: >>>> >>>> https://github.com/analytically/hadoop-ansible/blob/master/roles/2_ >>>> aggregated_links/tasks/main.yml >>>> >>>> Thanks! >>>> >>>> On Tuesday, 26 November 2013 21:46:43 UTC, James Tanner wrote: >>>>> >>>>> Show us your full ansible-playbook command+args and the playbook >>>>> please. >>>>> >>>>> On 11/26/2013 04:33 PM, Mathias Bogaert wrote: >>>>> >>>>> Here's my debug output for local_action: wait_for host={{ >>>>> inventory_hostname }} port=22 state=stopped : >>>>> >>>>> TASK: [2_aggregated_links | wait for the server to go down (reboot)] >>>>> ********** >>>>> <127.0.0.1> EXEC ['/bin/sh', '-c', 'mkdir -p >>>>> $HOME/.ansible/tmp/ansible-1385501543.62-188179043733979 && chmod >>>>> a+rx $HOME/.ansible/tmp/ansible-1385501543.62-188179043733979 && echo >>>>> $HOME/.ansible/tmp/ansible-1385501543.62-188179043733979'] >>>>> <127.0.0.1> REMOTE_MODULE wait_for host=hslave02 port=22 >>>>> state=stopped >>>>> <127.0.0.1> PUT /tmp/tmpBfFpk0 TO /home/mathias/.ansible/tmp/ >>>>> ansible-1385501543.62-188179043733979/wait_for >>>>> <127.0.0.1> EXEC /bin/sh -c 'sudo -k && sudo -H -S -p "[sudo via >>>>> ansible, key=zmxhtofymhnomrenapokmumehaihldle] password: " -u root >>>>> /bin/sh -c '"'"'echo SUDO-SUCCESS-zmxhtofymhnomrenapokmumehaihldle; >>>>> /usr/bin/python >>>>> /home/mathias/.ansible/tmp/ansible-1385501543.62-188179043733979/wait_for; >>>>> >>>>> rm -rf /home/mathias/.ansible/tmp/ansible-1385501543.62-188179043733979/ >>>>> >/dev/null 2>&1'"'"'' >>>>> failed: [hslave02] => {"failed": true, "item": "", "parsed": false} >>>>> invalid output was: [sudo via ansible, key= >>>>> zmxhtofymhnomrenapokmumehaihldle] password: >>>>> >>>>> Regards, >>>>> >>>>> Mathias >>>>> >>>>> On Monday, 25 November 2013 22:04:02 UTC, James Tanner wrote: >>>>>> >>>>>> It's not immediately obvious to me what error you are pointing out. >>>>>> Run >>>>>> ansible-playbook with -vvvv and show us that output. >>>>>> >>>>>> On 11/25/2013 04:50 PM, Mathias Bogaert wrote: >>>>>> > Hi, >>>>>> > >>>>>> > Using Ansible 1.3, the following worked: >>>>>> > >>>>>> > - name: reboot after bonding the interfaces >>>>>> > shell: sleep 2s && /sbin/reboot & >>>>>> > >>>>>> > - name: wait for the server to go down (reboot) >>>>>> > local_action: wait_for host={{ inventory_hostname }} port=22 >>>>>> > state=stopped >>>>>> > >>>>>> > - name: wait for the server to come up >>>>>> > local_action: wait_for host={{ inventory_hostname }} port=22 >>>>>> delay=30 >>>>>> > >>>>>> > Using Ansible 1.4, I get the following: >>>>>> > >>>>>> > TASK: [2_aggregated_links | reboot after bonding the interfaces] >>>>>> > ************** >>>>>> > changed: [hmaster02] >>>>>> > changed: [hslave02] >>>>>> > changed: [hslave01] >>>>>> > changed: [hmaster01] >>>>>> > changed: [hslave03] >>>>>> > changed: [hslave06] >>>>>> > changed: [hslave05] >>>>>> > changed: [hslave04] >>>>>> > >>>>>> > TASK: [2_aggregated_links | wait for the server to go down >>>>>> (reboot)] >>>>>> > ********** >>>>>> > failed: [hmaster02] => {"failed": true, "item": "", "parsed": >>>>>> false} >>>>>> > invalid output was: [sudo via ansible, >>>>>> > key=tefdvlddkmvonwuegpwdjbzabsvrxcml] password: >>>>>> > >>>>>> > failed: [hmaster01] => {"failed": true, "item": "", "parsed": >>>>>> false} >>>>>> > invalid output was: [sudo via ansible, >>>>>> > key=jussicehycjmhqzjbacrslyklbzhtduh] password: >>>>>> > >>>>>> > failed: [hslave01] => {"failed": true, "item": "", "parsed": false} >>>>>> > failed: [hslave03] => {"failed": true, "item": "", "parsed": false} >>>>>> > invalid output was: [sudo via ansible, >>>>>> > key=iuolakaoetpwrtjecgltrkoddrvubtoe] password: >>>>>> > >>>>>> > invalid output was: [sudo via ansible, >>>>>> > key=vyctfmxdrtgxiokmhxjnnritjltppzwb] password: >>>>>> > >>>>>> > failed: [hslave02] => {"failed": true, "item": "", "parsed": false} >>>>>> > invalid output was: [sudo via ansible, >>>>>> > key=jkjvdcurogwhljtamwlnknknvemivzsf] password: >>>>>> > >>>>>> > failed: [hslave06] => {"failed": true, "item": "", "parsed": false} >>>>>> > invalid output was: [sudo via ansible, >>>>>> > key=nnywazrfrszhxbdtvqyxdcppgwvzufwt] password: >>>>>> > >>>>>> > failed: [hslave04] => {"failed": true, "item": "", "parsed": false} >>>>>> > invalid output was: [sudo via ansible, >>>>>> > key=erxobssvkstyefvsdkkbwooyiglhkpgv] password: >>>>>> > >>>>>> > failed: [hslave05] => {"failed": true, "item": "", "parsed": false} >>>>>> > invalid output was: [sudo via ansible, >>>>>> > key=kxtdwcxkcxiexcheiksgqnlodcntcjmu] password: >>>>>> > >>>>>> > What should I change in my playbook? >>>>>> > >>>>>> > Thanks, >>>>>> > >>>>>> > Mathias >>>>>> > -- >>>>>> > 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]. >>>>>> > For more options, visit https://groups.google.com/groups/opt_out. >>>>>> >>>>>> -- >>>>> 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]. >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>>> >>>>> -- >>> 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]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> >> >> -- >> Michael DeHaan <[email protected]> >> CTO, AnsibleWorks, Inc. >> http://www.ansibleworks.com/ >> >> -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
