The full traceback is:
Could not add member(s) to one or more ADGroup.
At line:82 char:9
+ Add-ADPrincipalGroupMembership -Identity $group_member -Membe ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (Microsoft.Activ...ement.
ADGroup[]:ADGroup[]) [Add-ADPrincipalGroupMembership], ADException
+ FullyQualifiedErrorId : 1,Microsoft.ActiveDirectory.Management.
Commands.AddADPrincipalGroupMembership
ScriptStackTrace:
at <ScriptBlock>, <No file>: line 82
Microsoft.ActiveDirectory.Management.ADException: Could not add member(s)
to one or more ADGroup.
at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(
ErrorRecord errorRecord)
fatal: [ansible01.domain.DEV]: FAILED! => {
"changed": false,
"msg": "Unhandled exception while executing module: Could not add
member(s) to one or more ADGroup."
}
On Monday, February 10, 2020 at 4:22:50 PM UTC-5, Jesse Lyon wrote:
>
> My bad on linking to the wrong issue :)
>
> I've pulled it down and am giving it a shot now, will have results and
> comment on the PR if successful... so far I'm fighting the woes of a
> stripped down dev domain.
>
> Thanks again Jordan.
>
> On Monday, February 10, 2020 at 2:03:12 PM UTC-5, Jordan Borean wrote:
>>
>> Looks like I jumped the gun with closing that issue, the backported issue
>> referenced is for a separate problem. The actual cross domain support of
>> groups is still not supported in the module. There is a PR which you can
>> try out https://github.com/ansible/ansible/pull/65138 and comment on if
>> it solves your issue.
>>
>
--
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/f537749f-19ae-4d6d-835c-c12c0f29ba4f%40googlegroups.com.
