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
Problem Description:
Customer likes to use Ansible to push the configurations to stage them on NDFC (with "deploy=flase") and then deploy them from NDFC during the maintenance window. Using the VRF script (ndfc_vrf ansible script downloaded from cisco.dcnm.dcnm_policy),
customer is passing the vlan_id as a parameter from the Ansible script ,but vlan_id is not populated on the NDFC, it remains blank and asks to click on the propose VLAN in the GUI, which causes a randomly available vlan or the next available VLAN but not the vlan that is supplied from the ansible script.
Community Note
Problem Description:
Customer likes to use Ansible to push the configurations to stage them on NDFC (with "deploy=flase") and then deploy them from NDFC during the maintenance window. Using the VRF script (ndfc_vrf ansible script downloaded from cisco.dcnm.dcnm_policy), customer is passing the vlan_id as a parameter from the Ansible script ,but vlan_id is not populated on the NDFC, it remains blank and asks to click on the propose VLAN in the GUI, which causes a randomly available vlan or the next available VLAN but not the vlan that is supplied from the ansible script.
Ansible Version and collection version
DCNM version
Affected module(s)
Ansible Playbook
Debug Output
Expected Behavior
Actual Behavior
Steps to Reproduce
References