To add to it,
Numerous other sections of this playbook run without issue as well.
I'm at a pretty confusing impasse
ok: [WORKER_NODE] => {
"changed": false,
"distinguished_name":
"CN=GG_GROUP_RO,OU=Groups-Global,OU=Groups,DC=DOMAIN,DC=ORG",
"invocation": {
"module_args": {
"attributes": {
"add": null,
"remove": {},
"set": {}
},
"category": null,
"description": "RO access to 'Path'",
"display_name": null,
"domain_credentials": [],
"domain_password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
"domain_server": "domain_server",
"domain_username": "[email protected]",
"homepage": null,
"identity": null,
"managed_by": null,
"members": null,
"name": "GG_GROUP_RO",
"path": "OU=Groups-global,OU=Groups,DC=DOMAIN,DC=org",
"protect_from_deletion": null,
"sam_account_name": null,
"scope": "global",
"state": "present"
}
},
"object_guid": "d629bf03-a60c-432c-96cf-0d11c483cad7",
"sid": "S-1-5-21-448539723-113007714-725345543-96904"
On Monday, August 5, 2024 at 5:09:05 PM UTC-4 [email protected] wrote:
> 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?
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/3486d9b9-1f2e-4053-843b-50924e418628n%40googlegroups.com.
