-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Provider produced inconsistent result after apply #81
Comments
After investigating, apparently the configuration name in the .tf file has changed from bridge0 to System Bridge, causing this error. Modifying the configuration string in the .tf file to lab_id = cml2_lab.mySim.id
label = "nat"
x = -480
y = -250
tags = ["services"]
nodedefinition = "external_connector"
configuration = "System Bridge" solves the error |
rschmied
added a commit
that referenced
this issue
Dec 28, 2023
- added support for "hide links" node resource property, fixes #80 - added external connector data source - fixed integration test for groups data source - return error for external connector configuration when device name is provided instead of "NAT" or "System Bridge", fixes #81 - updated all package dependencies - fix CPULimit property for UMS and ExtConn (they are now always NULL starting with 2.6.0) - some cosmetic and test changes
rschmied
added a commit
that referenced
this issue
Dec 28, 2023
- added support for "hide links" node resource property, fixes #80 - added external connector data source - fixed integration test for groups data source - return error for external connector configuration when device name is provided instead of "NAT" or "System Bridge", fixes #81 - updated all package dependencies - fix CPULimit property for UMS and ExtConn (they are now always NULL starting with 2.6.0) - some cosmetic and test changes - added a add-to-booted-lab lifecycle test - formatted codebase w/ gofumpt - removed cmlclient go.mod local replace and updated cmlclient to 0.0.22 in go.mod - added / updated docs and ran generate - bumped go version to 1.21 in the workflows - added an extconn schema test - updated gh action components, only run one test suite in parallel
rschmied
added a commit
that referenced
this issue
Dec 28, 2023
- added support for "hide links" node resource property, fixes #80 - added external connector data source - fixed integration test for groups data source - return error for external connector configuration when device name is provided instead of "NAT" or "System Bridge", fixes #81 - updated all package dependencies - fix CPULimit property for UMS and ExtConn (they are now always NULL starting with 2.6.0) - some cosmetic and test changes - added a add-to-booted-lab lifecycle test - formatted codebase w/ gofumpt - removed cmlclient go.mod local replace and updated cmlclient to 0.0.22 in go.mod - added / updated docs and ran generate - bumped go version to 1.21 in the workflows - added an extconn schema test - updated gh action components, only run one test suite in parallel
rschmied
added a commit
that referenced
this issue
Dec 28, 2023
- added support for "hide links" node resource property, fixes #80 - added external connector data source - fixed integration test for groups data source - return error for external connector configuration when device name is provided instead of "NAT" or "System Bridge", fixes #81 - updated all package dependencies - fix CPULimit property for UMS and ExtConn (they are now always NULL starting with 2.6.0) - some cosmetic and test changes - added a add-to-booted-lab lifecycle test - formatted codebase w/ gofumpt - removed cmlclient go.mod local replace and updated cmlclient to 0.0.22 in go.mod - added / updated docs and ran generate - bumped go version to 1.21 in the workflows - added an extconn schema test - updated gh action components, only run one test suite in parallel
rschmied
added a commit
that referenced
this issue
Dec 28, 2023
- added support for "hide links" node resource property, fixes #80 - added external connector data source - fixed integration test for groups data source - return error for external connector configuration when device name is provided instead of "NAT" or "System Bridge", fixes #81 - updated all package dependencies - fix CPULimit property for UMS and ExtConn (they are now always NULL starting with 2.6.0) - some cosmetic and test changes - added a add-to-booted-lab lifecycle test - formatted codebase w/ gofumpt - removed cmlclient go.mod local replace and updated cmlclient to 0.0.22 in go.mod - added / updated docs and ran generate - bumped go version to 1.21 in the workflows - added an extconn schema test - updated gh action components, only run one test suite in parallel
rschmied
added a commit
that referenced
this issue
Dec 29, 2023
- added support for "hide links" node resource property, fixes #80 - added external connector data source - fixed integration test for groups data source - return error for external connector configuration when device name is provided instead of "NAT" or "System Bridge", fixes #81 - updated all package dependencies - fix CPULimit property for UMS and ExtConn (they are now always NULL starting with 2.6.0) - some cosmetic and test changes - added a add-to-booted-lab lifecycle test - formatted codebase w/ gofumpt - removed cmlclient go.mod local replace and updated cmlclient to 0.0.22 in go.mod - added / updated docs and ran generate - bumped go version to 1.21 in the workflows - added an extconn schema test - updated gh action components, only run one test suite in parallel
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
when deploying on CML 2.6, I get the error:
│ When applying changes to module.tenants.module.tenant_cml[0].cml2_node.bkn, provider "provider["registry.terraform.io/ciscodevnet/cml2"]" produced an unexpected new value: .configuration: was
│ cty.StringVal("bridge0"), but now cty.StringVal("System Bridge").
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
Unfortunately it does not provide more info.
The text was updated successfully, but these errors were encountered: