Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Bug Fixes

  • Device synchronization failure after restoring a database backup (rare condition)—In rare cases, restoring a database backup to a newly deployed system using the same management IP address and hostname (FQDN) as the original instance caused device configurations to fail resynchronizing automatically. This issue is now resolved.

  • Security policy deployment fails due to stale rule metadata—Security policy deployment might fail with an “application or application-set not found” error due to outdated rule metadata after modifying a rule’s zone pair. This caused mismatched configurations. This issue is now resolved.

  • Firewall rule analysis incorrectly mark rules as unused in multi-device policies—Firewall rule analysis might incorrectly mark a rule as unused if any device in a multi-device policy had no hits, ignoring activity on other devices. Organization-level thresholds were also applied incorrectly. This issue is now resolved. Rule analysis now considers hit activity across all devices and marks rules as unused only when no hits occur within the defined threshold period.

  • Resolve device configuration hangs on SRX Series Firewalls—Previously, the resolve device configuration operation on SRX Series Firewalls could hang in a loading state and fail to process changes or report errors. This is because of the parsing issues when response data was received in separate chunks. This issue is resolved now.

  • Upgrade failures leaving system in an inconsistent or stuck state—During an upgrade of Juniper Security Director, the upgrade process could fail or be interrupted, leaving the system stuck in an upgrading or inconsistent state. Subsequent upgrade attempts could also fail, and application and infrastructure services might not come up. This issue is now resolved.

    Kubernetes services incorrectly reported as DOWN or degraded after upgrade—After upgrading Juniper Security Director, the Kubernetes control plane or services could incorrectly appear as down or degraded in the UI, even though the cluster was functioning properly. This issue is now resolved.