-
Notifications
You must be signed in to change notification settings - Fork 157
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
The type being used for parsing should be uint32, not int32 #46
Comments
Integer options in Ansible have traditionally always been a signed integer
So technically you should be able to do Unfortunately when testing this with the following playbook I've encounted another issue that stops it from working.
The problem is that the code that is returning the exit code back to
A fourth option could be a combination of the 2 and have the |
I ended up going to option 3 as that was the least obtrusive change required. The PR that implements this fix is #47. |
Thanks for mentioning the possible workaround of using the negative... I had thought of and tried that, and noticed the same problem you noted. Thanks for preparing the PR! |
From @wsteinford on Apr 07, 2020 01:45
ISSUE TYPE
Bug Report
ANSIBLE VERSION
ansible 2.9
CONFIGURATION
OS / ENVIRONMENT
Deploying to Windows host
SUMMARY
https://github.com/ansible/ansible/blob/18a2183a0be3896f28b9fc77f90563585916e98c/lib/ansible/modules/windows/win_package.ps1#L65
This should use uint32 because the function MsiOpenPackageW returns uint32:
It causes a failure if the expected value exceeds 31 bits, though it should be allowed to reach 32 bits.
STEPS TO REPRODUCE
EXPECTED RESULTS
The installer runs and returns 3221225477, and Ansible accepts it as OK
ACTUAL RESULTS
Ansible returns the message:
Copied from original issue: ansible/ansible#68732
The text was updated successfully, but these errors were encountered: