-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
Option system=yes not honored for module group. #2836
Comments
Thanks! Please submit this as a pull request. |
Done. As it was my first pull request on github, please let me know if I made any mistakes. |
mpdehaan
added a commit
that referenced
this issue
May 5, 2013
Fix #2836. Ensure proper handling of option "system=yes" in module "grou...
merged in, thanks! |
jimi-c
pushed a commit
that referenced
this issue
Dec 6, 2016
* Add oVirt module to manage VMs This patch add oVirt module to manage Virtual Machines * Add oVirt module to manage authentication This patch add oVirt module to manage authentication * Add oVirt module to manage disks * Added VM state management and fixups
robinro
pushed a commit
to robinro/ansible
that referenced
this issue
Dec 9, 2016
* Add oVirt module to manage VMs This patch add oVirt module to manage Virtual Machines * Add oVirt module to manage authentication This patch add oVirt module to manage authentication * Add oVirt module to manage disks * Added VM state management and fixups
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was trying to create a new system group (gid<1000), however the system was always selecting a non-system gid for the new group. After debugging a bit a was able to track down the problem as mistaken comparison between a boolean (True) and string "yes"). The changes bellow would fix the issue:
Best regards,
Luciano
The text was updated successfully, but these errors were encountered: