So I’m working on converting to the new modules as the title states.
I’ve run into some VERY unexpected behavior going from the old modules to new, namely do these adhere to the Desired state mindset or is that gone?
When attempting to execute a play against a group that is already existing (re-running the playbook) I’ve ran into the below.
fatal: [WORKER_NODE]: FAILED! => {
“changed”: false,
“distinguished_name”: null,
“invocation”: {
“module_args”: {
“attributes”: {
“add”: {},
“remove”: {},
“set”: {}
},
“category”: null,
“description”: “RO access to ‘\path’”,
“display_name”: null,
“domain_credentials”: ,
“domain_password”: “VALUE_SPECIFIED_IN_NO_LOG_PARAMETER”,
“domain_server”: “DC”,
“domain_username”: “ACCOUNT”,
“homepage”: null,
“identity”: null,
“managed_by”: null,
“members”: null,
“name”: “GROUP_NAME”,
“path”: “OU=Groups-universal,OU=Groups,DC=DOMAIN,DC=org”,
“protect_from_deletion”: null,
“sam_account_name”: null,
“scope”: “universal”,
“state”: “present”
}
},
“msg”: “New-ADGroup failed: The specified group already exists”,
“object_guid”: null
I used to be able to simply execute the job and step through issues without needing to cleanup the group each time.
Am I doing something wrong here or is this the new norm?