Skip to content
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

Running terraform apply on srx causes "Warning: Config Clear/Unlock Warning" #710

Closed
luke-oqc opened this issue Sep 26, 2024 · 1 comment · Fixed by #711
Closed

Running terraform apply on srx causes "Warning: Config Clear/Unlock Warning" #710

luke-oqc opened this issue Sep 26, 2024 · 1 comment · Fixed by #711
Assignees
Labels
bug Something isn't working
Milestone

Comments

@luke-oqc
Copy link

luke-oqc commented Sep 26, 2024

Terraform and Provider Versions

Terraform v1.9.6
on windows_amd64

  • provider registry.terraform.io/jeremmfr/junos v2.9.0

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

  1. 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

@luke-oqc luke-oqc added the bug Something isn't working label Sep 26, 2024
@jeremmfr
Copy link
Owner

Hi @luke-oqc 👋 , thanks for reporting this.

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.

I'll take care of removing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants