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
Terraform Version
Terraform v1.6.1-dev
on linux_amd64
- provider registry.terraform.io/ciscodevnet/dcnm v1.2.7
Your version of Terraform is out of date! The latest version
is 1.6.1. You can update by downloading from https://www.terraform.io/downloads.html
NDFC version
Affected Resource(s)
Terraform Configuration Files
See the following repo:
https://github.com/cisco-apjc-cloud-se/ndfc-automation-lab-v2/tree/main/terraform
Debug Output
Plan: 0 to add, 2 to change, 0 to destroy.
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value: yes
dcnm_vrf.vrf-2: Modifying... [id=TERRAFORM-VRF2]
dcnm_vrf.vrf-1: Modifying... [id=TERRAFORM-VRF1]
╷
│ Error: VRF record is created but not deployed yet. Error while attachment : SUCCESS Peer attach Response - SUCCESS
│
│ with dcnm_vrf.vrf-1,
│ on 2-vrfs.tf line 2, in resource "dcnm_vrf" "vrf-1":
│ 2: resource "dcnm_vrf" "vrf-1" {
│
╵
╷
│ Error: VRF record is created but not deployed yet. Error while attachment : SUCCESS Peer attach Response - SUCCESS
│
│ with dcnm_vrf.vrf-2,
│ on 2-vrfs.tf line 114, in resource "dcnm_vrf" "vrf-2":
│ 114: resource "dcnm_vrf" "vrf-2" {
│
╵
Expected Behavior
A dcnm_vrf resource with both attachments blocks (with attachments.attach = true) and deploy = true should both create the VRF, create VRF attachments and deploy the VRFs to the selected switches.
Actual Behavior
When deploy = true is set, the error "Error: VRF record is created but not deployed yet. Error while attachment : SUCCESS Peer attach Response - SUCCESS" is generated. In NDFC, the configuration of both the VRF and VRF attachments is shown as "out-of-sync". No configuration is actually deployed from NDFC.
Triggering deploy from NDFC will show the pending configuration and will deploy successfully.
After manually deploying, running terraform plan or terraform apply show no changes to the infrastructure.
Steps to Reproduce
terraform apply
NOTE: the .2-vrfs.tf file is hidden in the directory and needs to be unhidden (i.e. renamed to remove the . prefix)
Important Factoids
This code was previously working with earlier versions of NDFC (12.0) and Terraform (~1.3?)
Community Note
Terraform Version
Terraform v1.6.1-dev
on linux_amd64
Your version of Terraform is out of date! The latest version
is 1.6.1. You can update by downloading from https://www.terraform.io/downloads.html
NDFC version
Affected Resource(s)
Terraform Configuration Files
See the following repo:
https://github.com/cisco-apjc-cloud-se/ndfc-automation-lab-v2/tree/main/terraform
Debug Output
Expected Behavior
A dcnm_vrf resource with both attachments blocks (with attachments.attach = true) and deploy = true should both create the VRF, create VRF attachments and deploy the VRFs to the selected switches.
Actual Behavior
When deploy = true is set, the error "Error: VRF record is created but not deployed yet. Error while attachment : SUCCESS Peer attach Response - SUCCESS" is generated. In NDFC, the configuration of both the VRF and VRF attachments is shown as "out-of-sync". No configuration is actually deployed from NDFC.
Triggering deploy from NDFC will show the pending configuration and will deploy successfully.
After manually deploying, running
terraform planorterraform applyshow no changes to the infrastructure.Steps to Reproduce
terraform applyNOTE: the .2-vrfs.tf file is hidden in the directory and needs to be unhidden (i.e. renamed to remove the . prefix)
Important Factoids
This code was previously working with earlier versions of NDFC (12.0) and Terraform (~1.3?)