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.

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

win_user: Fails with Exception calling "SetInfo" with "0" argument(s) #20369

Closed
dagwieers opened this issue Jan 17, 2017 · 6 comments
Closed
Assignees
Labels
affects_2.3 This issue/PR affects Ansible v2.3 bug This issue/PR relates to a bug. module This issue/PR relates to a module. support:core This issue/PR relates to code supported by the Ansible Engineering Team. windows Windows community

Comments

@dagwieers
Copy link
Contributor

dagwieers commented Jan 17, 2017

ISSUE TYPE
  • Bug Report
COMPONENT NAME

win_user

ANSIBLE VERSION

v2.3

OS / ENVIRONMENT

Windows 2012 R2

SUMMARY

When using the below playbook (without password !) I get this error:

Exception calling "SetInfo" with "0" argument(s): "The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements."
- win_user:
    name: sqlsvc
    groups:
    - Administrators
    groups_action: add
    password_never_expires: yes
    state: present

Obviously I didn't provide a password, but it shouldn't bail out with this specific error.

@ansibot
Copy link
Contributor

ansibot commented Jan 17, 2017

@ansibot ansibot added affects_2.3 This issue/PR affects Ansible v2.3 bug_report module This issue/PR relates to a module. needs_triage Needs a first human triage before being processed. windows Windows community labels Jan 17, 2017
@nitzmahone nitzmahone removed the needs_triage Needs a first human triage before being processed. label Jan 19, 2017
@nitzmahone nitzmahone added this to the 2.2.0 milestone Jan 19, 2017
@gundalow gundalow modified the milestone: 2.2.0 Apr 13, 2017
@ansibot ansibot added the support:core This issue/PR relates to code supported by the Ansible Engineering Team. label Jun 29, 2017
@ansibot
Copy link
Contributor

ansibot commented Jul 19, 2017

@jhawkesworth
Copy link
Contributor

At 19:00 UTC on Tuesday 19 September 2017 this ticket will be processed during the second Windows Sprint,
https://github.com/ansible/community/wiki/Windows:-sprints
we would appreciate if you could join the Sprint to help out with understanding/fixing/closing this issue.

@jhawkesworth
Copy link
Contributor

Discussed at the sprint @dagwieers will attempt to reproduce.

@dagwieers
Copy link
Contributor Author

dagwieers commented Sep 21, 2017

I can reproduce this on Windows 2012 R2, but not on Windows 10 (latest update).

So I wonder how we can solve this:

  1. Not providing a password is possible on other platforms (even when the user exists)
  2. Provide a proper error message without the wrapping Improve Windows module exception output #28402

@dagwieers
Copy link
Contributor Author

So I am going to close this one and refer to #28402 to ensure we have proper error-messages in the future for run-away exceptions :-)

@ansibot ansibot added bug This issue/PR relates to a bug. and removed bug_report labels Mar 7, 2018
@ansible ansible locked and limited conversation to collaborators Apr 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.3 This issue/PR affects Ansible v2.3 bug This issue/PR relates to a bug. module This issue/PR relates to a module. support:core This issue/PR relates to code supported by the Ansible Engineering Team. windows Windows community
Projects
None yet
Development

No branches or pull requests

5 participants