This repository has been archived by the owner on Dec 26, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 200
semodule ssh_password error on AWS Centos 7 #64
Labels
Comments
Hi @mikerj1, thanks for bringing this up.
When this task does not run, the variable I'm going to change the task so this won't happen! |
Awesome, thanks! Is it as simple as adding always_run: true to the task? |
Yes and I also add a
EDIT: Or would you like to create a PR? |
This looks like it will solve the problem and you've got it staged, so please proceed. Thanks again. |
rndmh3ro
pushed a commit
that referenced
this issue
May 20, 2016
rndmh3ro
pushed a commit
that referenced
this issue
Jun 13, 2016
rndmh3ro
pushed a commit
that referenced
this issue
Jun 13, 2016
add always_run: true to task. fix #64
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello - I'm seeing the error below and I'm not sure if I'm doing something wrong or if this is a bug. The server is the official Centos7 image on AWS. The error is observed when running ansible-playbook with --check.
Running the following on the server (which appears to be part of the problem) shows no output.
semodule -l | grep "ssh_password" | awk '{print $3}'
These are the module names I see with the string ssh:
semodule -l | grep "ssh"
rssh 2.3.0
ssh 2.4.2
Thanks!
Error:
fatal: [server1]: FAILED! => {"failed": true, "msg": "The conditional check 'sestatus.rc == 0 and sestatus.stdout != 'Disabled'' failed. The error was: error while evaluating conditional (sestatus.rc == 0 and sestatus.stdout != 'Disabled'): 'dict object' has no attribute 'rc'\n\nThe error appears to have been in '/Users/user1/RRS GDrive/Projects/corp1/repos/corp1-ansible/roles/hardening.ssh-hardening/tasks/main.yml': line 11, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: check the ssh_password policy state\n ^ here\n"}
The text was updated successfully, but these errors were encountered: