-
Notifications
You must be signed in to change notification settings - Fork 50
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
getting error "[node_check_object fail! for ring-rx 0]" when trying to modify interface configuration #336
Comments
Hi @rasanentimo , Thank you for bringing up this issue. I was able to reproduce it, and it seems that the default value of ring-rx is set to 0. When you update the port, Terraform attempts to send 0 to FOS, but FOS does not accept 0 as a valid value; it only supports values between 1 and 1024. As a temporary solution, could you try using a generic resource? I have reported this to the development team for further investigation and resolution.
Thanks, |
I'm just trying things out, so I can wait for the resolution for this issue. Is it also expected that the changes made with terraform are not removed when running 'terraform destroy' or just removing/commenting out certain lines from terraform? I see that the terraform state is modified but there's no changes on the FOS configuration, i.e. the interface config remains as it is. |
I made another test by creating custom FW service based on this, https://registry.terraform.io/providers/fortinetdev/fortios/latest/docs/resources/fortios_firewallservice_custom, and it fails as well
Could this be related to the FOS version being used, i.e. 7.6.0? |
Hi @rasanentimo , Thank you very much for your questions. For created objects such as firewall policies, static routes, etc., using Regarding the Please feel free to let me know if you have further questions or need additional clarification.
Thanks, |
Hi @MaxxLiu22! Thanks for the quick reply! I can confirm that changing the protocol from ""TCP/UDP/SCTP" to "TCP/UDP/UDP-Lite/SCTP" solved the issue of creating the custom service. Here's the steps which I tried for the modifying the interface. initial state, i.e no IP address configured
Run terraform
and the interface is configured with an IP
Comment out the changes and run terraform again
However, the changes are not reverted back
Although terraform lists it on the actions to be performed
Is this expected behaviour or could this be related to some changes with 7.6.0 as well? |
Description
I'm trying to modify interface configuration with fortios provider but getting following error
Terraform and fortios provider version:
Expected result
Interface configuration changed.
Steps To Reproduce
Configure interface
Interface configuration is accepted.
Modify, for example, interface description
However, if I run 'terraform destroy' and then again 'terraform apply', the changes are applied. Although 'terraform destroy' doesn't remove any of the applied configurations from the FW configuration
The text was updated successfully, but these errors were encountered: