Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

sysctl's first run on Fedora 19 fails, all following runs pass #3931

Closed
maxamillion opened this issue Aug 23, 2013 · 2 comments
Closed

sysctl's first run on Fedora 19 fails, all following runs pass #3931

maxamillion opened this issue Aug 23, 2013 · 2 comments
Labels
bug This issue/PR relates to a bug.

Comments

@maxamillion
Copy link
Contributor

The following task:

- name: sysctl - kernel.sem 
  sysctl: name=kernel.sem state=present value="250  32000 32  4096"
          reload=yes

For some reason on a fresh install of Fedora 19 (fully yum updated), the first run (only the first run) of the sysctl task fails with the following error. All following runs succeed but next time I fire up a new machine, it fails on that one for the first run.

TASK: [sysctl - kernel.sem] *************************************************** 
<10.3.1.55> ESTABLISH CONNECTION FOR USER: fedora
<10.3.1.55> EXEC ['ssh', '-tt', '-q', '-o', 'ControlMaster=auto', '-o', 'ControlPersist=60s', '-o', 'ControlPath=/tmp/ansible-ssh-%h-%p-%r', '-o', 'Port=22', '-o', 'KbdInteractiveAuthentication=no', '-o', 'PasswordAuthentication=no', '-o', 'User=fedora', '-o', 'ConnectTimeout=10', '10.3.1.55', "/bin/sh -c 'mkdir -p $HOME/.ansible/tmp/ansible-1377279891.27-177819883622047 && chmod a+rx $HOME/.ansible/tmp/ansible-1377279891.27-177819883622047 && echo $HOME/.ansible/tmp/ansible-1377279891.27-177819883622047'"]
<10.3.1.55> REMOTE_MODULE sysctl name=kernel.sem state=present value="250  32000 32  4096" reload=yes
<10.3.1.55> PUT /tmp/tmp5sjjwE TO /home/fedora/.ansible/tmp/ansible-1377279891.27-177819883622047/sysctl
<10.3.1.55> EXEC ['ssh', '-tt', '-q', '-o', 'ControlMaster=auto', '-o', 'ControlPersist=60s', '-o', 'ControlPath=/tmp/ansible-ssh-%h-%p-%r', '-o', 'Port=22', '-o', 'KbdInteractiveAuthentication=no', '-o', 'PasswordAuthentication=no', '-o', 'User=fedora', '-o', 'ConnectTimeout=10', '10.3.1.55', '/bin/sh -c \'sudo -k && sudo -H -S -p "[sudo via ansible, key=pzwyazdooeqcutbuqxjnaybyzoghnjlu] password: " -u root /bin/sh -c \'"\'"\'/usr/bin/python /home/fedora/.ansible/tmp/ansible-1377279891.27-177819883622047/sysctl; rm -rf /home/fedora/.ansible/tmp/ansible-1377279891.27-177819883622047/ >/dev/null 2>&1\'"\'"\'\'']
failed: [10.3.1.55] => {"failed": true, "item": ""}
msg: checks_after failed with: key seems not set to value even after update/sysctl, founded : <250 32000 32 4096>, wanted : <250  32000 32  4096>

FATAL: all hosts have already failed -- aborting
@jimi-c
Copy link
Member

jimi-c commented Aug 23, 2013

That's interesting, they seem to not be agreeing on the number of spaces.

@mpdehaan
Copy link
Contributor

FWIW, you could set "ignore_errors: True" here, but I'm not sure what the right check would be if it's not echoing back quite the same.

@jimi-c jimi-c closed this as completed in 3e9b63f Sep 11, 2013
@ansibot ansibot added bug This issue/PR relates to a bug. and removed bug_report labels Mar 6, 2018
@ansible ansible locked and limited conversation to collaborators Apr 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug This issue/PR relates to a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mpdehaan @jimi-c @maxamillion @ansibot