cisco.aci.aci_static_binding_to_epg module Bug

[arammoreno]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

• When executing the module "cisco.aci.aci_static_binding_to_epg module" of the cisco.aci 2.8.0 module, it returns an error of the DN= the module, }, "msg": "APIC Error 102: configured object ((Dn0)) not found Dn0=uni/tn-xxx/ap-xx/epg-xx/rspathAtt-[topology/pod-1/paths-201/pathep-[ eth1/84]], "

The problem is that the Ansible ACI module introduces a DN0= when it should be DN=

This would be the object I should use example,

dn="xx/tn-xx/ap-xx/epg-xx/rspathAtt-[topology/pod-1/paths-201/pathep-[eth1/84]]"

Affected Module Name(s):

• cisco.aci.aci_static_binding_to_epg module

APIC version and APIC Platform

• Version 6.0(3e)

Collection versions

• cisco.aci 2.8.0

Output/ Error message

*

Expected Behavior

*

Actual Behavior

*

Playbook tasks to Reproduce

• • name: Get specific Static Path binding for given EPG LEAF01-ETH1_84 cisco.aci.aci_static_binding_to_epg: host: "{{ hostname }}" username: "{{ admin_username }}" password: "{{ admin_password }}" tenant: "{{ tenant }}" ap: "{{ app }}" epg: "{{ EPG_75 }}" encap_id: "{{ VLAN_75 }}" deploy_immediacy: immediate interface_mode: tagged interface_type: switch_port pod: 1 leafs: "{{ LEAF01 }}" interface: "{{ interface1_84 }}" state: present validate_certs: false delegate_to: localhost

Important Factoids

References

• I have not found any similar case

[shrsr]

@arammoreno Thank you for opening the issue. Did you start facing this after updating aci collection to v2.8.0?

Did you mean to use state: query in the task of your playbook?

[akinross]

@arammoreno, could you also provide the variables that you are passing in to interface argument? Where is this coming from and could it be prepended with a space character? Furthermore could you share logs of the tasks during your playbook execution with a higher verbosity level?

[arammoreno]

Hi,

This infrastructure is new, both Ansible and ACI, so I ran into the problem right now for the first time.

I attach the variable data and the playbook records.

vars.txt task2_log.txt

[arammoreno]

Hi,

I'm sorry, I have performed a debug on my variables and the problem is that I was passing a variable wrong, which is why it failed, thank you for answering and apologizing.

best regards.

[akinross]

No worries and no need for an apology, these things happen sometimes. Good to hear your problem is resolved. I will close the issue.