You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
│ Warning: Config Clear/Unlock Warning
│
│ with junos_security_address_book.global,
│ on address-book.tf line 1, in resource "junos_security_address_book" "global":
│ 1: resource "junos_security_address_book" "global" {
│
│ config clear:
│ Delete all fabric member interfaces on node0/node1 will cause session state sync failure/traffic black hole
Steps to Reproduce
running terraform apply on above terraform config on srx chassis cluster
terraform apply
Additional Context
When running locally on the device -
set security address-book global description "test"
commit confirmed 5
node0:
configuration check succeeds
commit confirmed will be automatically rolled back in 5 minutes unless confirmed
node1:
commit complete
commit confirmed will be automatically rolled back in 5 minutes unless confirmed
node0:
commit complete
After a few tests, an RPC Command to delete the candidate configuration is sent before unlocking it, but it seems useless and may produce this kind of warning.
Terraform and Provider Versions
Terraform v1.9.6
on windows_amd64
Terraform Configuration Files
resource "junos_security_address_book" "global" {
name = "global"
description = "test"
}
Expected Behavior
This should just apply, no warnings
Actual Behavior
│ Warning: Config Clear/Unlock Warning
│
│ with junos_security_address_book.global,
│ on address-book.tf line 1, in resource "junos_security_address_book" "global":
│ 1: resource "junos_security_address_book" "global" {
│
│ config clear:
│ Delete all fabric member interfaces on node0/node1 will cause session state sync failure/traffic black hole
Steps to Reproduce
running terraform apply on above terraform config on srx chassis cluster
terraform apply
Additional Context
When running locally on the device -
set security address-book global description "test"
commit confirmed 5
node0:
configuration check succeeds
commit confirmed will be automatically rolled back in 5 minutes unless confirmed
node1:
commit complete
commit confirmed will be automatically rolled back in 5 minutes unless confirmed
node0:
commit complete
commit confirmed will be rolled back in 5 minutes
commit check
node0:
configuration check succeeds
node1:
configuration check succeeds
References
The text was updated successfully, but these errors were encountered: