---
type: Addressed
product: PAN-OS
version: 10.2.1
source: common-crawl
crawl: CC-MAIN-2026-12
---

## WF500-5781

The WildFire appliance might erroneously generate and log the following device certification error: Device certificate is missing or invalid. It cannot be renewed.

## WF500-5754

In WildFire appliance clusters, issuing the show cluster controller CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.

**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).

## WF500-5632

The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.

## PAN-297610

A firewall may become unresponsive after an upgrade due to the fsck command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.

## PAN-297295

```caveat
VM-Series firewalls in Microsoft Azure environments only
```

After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a segfault error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.

**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:

- D3_v2/DS3_v2 to D8ds_v5
- D4_v2/DS4_v2 to D8ds_v5
- D5_v2/DS5_v2 to D16ds_v5

Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.

## PAN-295255

Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.

## PAN-291716

```caveat
This issue is now resolved. See PAN-OS 10.2.17 Addressed Issues.
```

During a commit, the firewall experiences an out-of-memory (OOM) condition due to a memory leak and displays an error message. This issue causes the device to crash and reboot unexpectedly.

## PAN-291288

```caveat
This issue is now resolved. See PAN-OS 10.2.16-h6 Addressed Issues
```

A memory leak in the configd process might lead to an active firewall to reboot due to an Out-of-Memory (OOM) condition. This issue is observed when specific status commands, such as request log-collector forwarding status are executed at high frequencies.

## PAN-288097

```caveat
Firewalls in HA configurations only
```

Routed process may stop responding after changing MTU or any link parameters when OSPF and PIM are enabled on the same interface.

## PAN-286231

When performing a partial **Commit and Push** on Panorama, there is a risk that unintended configuration changes might be pushed to a firewall.

This issue is more likely to occur in the following scenarios:

- When you run **Commit and Push** operations as a single action.
- When you trigger multiple parallel commit-all jobs at the same time.
- Device groups and templates have different configuration synchronization versions.

**Workaround:** Perform one of the following steps:

- Perform commit and push as two separate, sequential steps.
- Perform a full push instead of selective push.

## PAN-284073

The firewall web interface becomes inaccessible and commits fail.

## PAN-284067

A cumulative memory leak in the devsrvr process gets progressively worse whenever the CLI command show running application statistics is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.

**Workaround:** Avoid using the CLI command: show running application statistics.

## PAN-281370

The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.

## PAN-260851

From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.

## PAN-259769

GlobalProtect portal is not accessible via a web browser and the app displays the error ERR_EMPTY_RESPONSE.

## PAN-250062

Device telemetry might fail at configured intervals due to bundle generation issues.

## PAN-243951

On the Panorama management sever in an active/passive High Availability (HA) configuration, managed devices (**Panorama** > **Managed Devices** > **Summary**) display as out-of-sync on the passive HA peer when configuration changes are made to the SD-WAN (**Panorama** > **SD-WAN**) configuration on the active HA peer.

**Workaround:** Manually synchronize the Panorama HA peers.

1. Log in to the [Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) on the active HA peer.
2. Select **Commit** and **Commit to Panorama** the SD-WAN configuration changes on the active HA peer.
  On the passive HA peer, select **Panorama** > **Managed Devices** > **Summary** and observe that the managed devices are now out-of-sync.
3. Log in to the primary HA peer [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and trigger a manual synchronization between the active and secondary HA peers.
  *request high-availability sync-to-remote running-config*
4. Log back in to the active HA peer Panorama web interface and select **Commit** > **Push to Devices** and **Push**.

## PAN-234408

Enterprise DLP cannot detect and block non-file based traffic for ChatGPT from traffic forwarded to the DLP cloud service from an NGFW.

## PAN-228273

```caveat
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
```

On the Panorama management server in FIPS-CC mode, the ElasticSearch cluster fails to come up and the show log-collector-es-cluster health command displays the status is red. This results in log ingestion issues for Panorama in Panorama only or Log Collector mode.

## PAN-227344

On the Panorama management server, PDF Summary Reports (**Monitor** > **PDF Reports** > **Manage PDF Summary**) display no data and are blank when predefined reports are included in the summary report.

## PAN-225337

```caveat
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
```

On the Panorama management server, the configuration push to a multi-vsys firewall fails if you:

1. Create a **Shared** and vsys-specific device group configuration object with an indentical name. For example, a **Shared** address object called SharedAO1 and a vsys-specific address object also called SharedAO1.
2. Reference the **Shared** object in another **Shared** configuration. For example, reference the **Shared** address object (SharedAO1) in a **Shared** address group called SharedAG1.
3. Use the **Shared** configuration object with the reference in a vsys-specific configuration. For example, reference the **Shared** address group (SharedAG1) in a vsys-specific policy rule.

**Workaround:** Select **Panorama** > **Setup** > **Management** and edit the Panorama Settings to enable one of the following:

- **Shared Unused Address and Service Objects with Devices**—This options pushes all **Shared** objects, along with device group specific objects, to managed firewalls.
  This is a global setting and applies to all managed firewalls, and may result in pushing too many configuration objects to your managed firewalls.
- **Objects defined in ancestors will take higher precedence**—This option specifies that in the event of objects with the same name, ancestor object take precedence over descendent objects. In this case, the **Shared** objects take precedence over the vsys-specific object.
  This is a global setting and applies to all managed firewalls. In the example above, if the IP address for the **Shared** SharedAO1 object was 10.1.1.1 and the device group specific SharedAO1 was 10.2.2.2, the 10.1.1.1 IP address takes precedence.

Alternatively, you can remove the duplicate address objects from the device group configuration to allow only the **Shared** objects in your configuration.

## PAN-223488

```caveat
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
```

Closed ElasticSearch shards are not deleted from a Panorama M-Series or virtual appliance. This causes the ElasticSearch shard purging to not work as expected, resulting in high disk usage.

## PAN-223365

The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.

**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.

admin debug elasticsearch es-restart all

## PAN-222586

On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.

## PAN-222253

```caveat
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
```

On the Panorama management server, policy rulebase reordering when you **View Rulebase by Groups** (**Policy** > **<policy-rulebase>**) does not persist if you reorder the policy rulebase by dragging and dropping individual policy rules and then moving the entire tag group.

## PAN-221775

A Malformed Request error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the Password includes an ampersand (&).

## PAN-221015

```caveat
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
```

On M-600 appliances in Panorama or Log Collector mode, the es-1 and es-2 ElasticSearch processes fail to restart when the M-600 appliance is rebooted. The results in the Managed Collector ES health status (**Panorama** > **Managed Collectors** > **Health Status**) to be degraded.

**Workaround:** [Log in to the Panorama or Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) experiencing degraded ElasticSearch health and restart all ElasticSearch processes.

admin>debug elasticsearch es-restart optional all

## PAN-219644

```caveat
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
```

Firewalls forwarding logs to a syslog server over TLS (**Objects** > **Log Forwarding**) use the default Palo Alto Networks certificate instead of the custom certificate configured on the firewall.

## PAN-218521

```caveat
This issue is now resolved. See PAN-OS 10.2.7 Addressed Issues.
```

The ElasticSearch process on the M-600 appliance in Log Collector mode may enter a continuous reboot cycle. This results in the M-600 appliance becoming unresponsive, consuming logging disk space, and preventing new log ingestion.

## PAN-217307

```caveat
This issue is now resolved. See PAN-OS 10.2.11 Addressed Issues.
```

The following Security policy rule (**Policies** > **Security**) filters return no results:

log-start eq no

log-end eq no

log-end eq yes

## PAN-215778

```caveat
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
```

On the M-600 appliance in Management Only mode, XML API Get requests for /config fail with the following error due to exceeding the [total configuration size](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/panorama-overview/centralized-firewall-configuration-and-update-management/total-configuration-size-for-panorama) supported on the M-600 appliance.

504 Gateway timeout

## PAN-215082

```caveat
This issue is now resolved. See PAN-OS 10.2.8 Addressed Issues.
```

M-300 and M-700 appliances may generate erroneous system logs (**Monitor** > **Logs** > **System**) to alert that the M-Series appliance memory usage limits are reached.

## PAN-213746

On the Panorama management server, the **Hostkey** displayed as undefined undefined if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.

## PAN-213119

PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):

show -> dis-block-table is unexpected

## PAN-212889

```caveat
This issue is now resolved. See PAN-OS 10.2.14 Addressed Issues
```

On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying no data to display when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.

## PAN-212533

Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from Superuser to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.

## PAN-211531

On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).

## PAN-209288

Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).

## PAN-208325

```caveat
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
```

The following NextGen firewalls and Panorama management server models are unable to automatically renew the device certificate (**Device** > **Setup** > **Management** or **Panorama** > **Setup** > **Management**).

- M-300 and M-700
- PA-410 Firewall
- PA-440, PA-450, and PA-460 Firewalls
- PA-3400 Series
- PA-5410, PA-5420, and PA-5430 Firewalls
- PA-5450 Firewall

**Workaround:** Log in to the [firewall CLI](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-cli-quick-start/get-started-with-the-cli/access-the-cli) or [Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and fetch the device certificate.

admin>request certificate fetch

## PAN-207629

```caveat
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
```

On the Panorama management server, selective push fails to managed firewalls if the managed firewalls are enabled with multiple vsys and the Push Scope contains shared objects in device groups.

## PAN-206268

On the Panorama management server, the Auth Key field was erroneously displayed when you configure the Panorama Settings (**Device** > **Setup** > **Management**) as part of a template or template stack configuration.

## PAN-206253

```caveat
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
```

For PA-3400 Series firewalls, the default log rate is set too low and the max configurable log rate is incorrectly capped resulting in the firewall not generating more than 6,826 logs per second.

## PAN-206243

```caveat
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
```

The PA-220 firewall reaches the maximum disk usage capacity multiple a day that requires a disk cleanup. A critical system log (**Monitor** > **Logs** > **System**) is generated each time the firewall reaches maximum disk usage capacity.

## PAN-205187

```caveat
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
```

ElasticSearch may not start properly when a newly installed Panorama virtual appliance powers on for the first time, resulting in the Panorama virtual appliance being unable to query logs forwarded from the managed firewall to a Log Collector.

**Workaround:** [Log in to the Panorama CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and start the PAN-OS software.

admin>request restart software

## PAN-204663

```caveat
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
```

On the Panorama management server, you are unable to Context Switch from one managed firewall to another.

**Workaround:** After you Context Switch to a managed firewall, you must first Context Switch back to Panorama before you can continue to Context Switch to a different managed firewall.

## PAN-201855

```caveat
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
```

On the Panorama management server, cloning any template (**Panorama** > **Templates**) corrupts certificates (**Device** > **Certificate Management** > **Certificates**) with the **Block Private Key Export** setting enabled across all templates. This results in managed firewalls experiencing issues wherever the corrupted certificate is referenced.

For example, you have template A, B, and C where templates A and B have certificates with the **Block Private Key Export** setting enabled. Cloning template C corrupts the certificates with **Block Private Key Export** setting enabled in templates A and B.

**Workaround:** After cloning a template, delete and re-import the corrupted certificates.

## PAN-199557

```caveat
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
```

On M-600 appliances in an Active/Passive high availability (HA) configuration, the configd process restarts due to a memory leak on the Active Panorama HA peer. This causes the Panorama web interface and CLI to become unresponsive.

**Workaround:** Manually reboot the Active Panorama HA peer.

## PAN-197097

Large Scale VPN (LSVPN) does not support IPv6 addresses on the satellite firewall.

## PAN-196758

On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).

## PAN-194826

```caveat
WF-500 appliance only
```

System log forwarding does not work over a TLS connection.

## PAN-194708

```caveat
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
```

URL filtering logs (**Monitor** > **Logs** > **URL Filtering**) erroneously truncate a 16KB Header value and do not display the Header values that follow the truncated 16KB header.

For example, a URL filtering log has 5 Headers. The second Header has a 16KB value. In the URL filtering log, the first header and the value are displayed, second Header value is truncated, and remaining three headers are not displayed.

## PAN-194519

```caveat
PA-5450 firewall only
```

Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.

## PAN-194515

```caveat
PA-5450 firewall only
```

The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.

**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.

## PAN-193251

```caveat
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
```

If SAML is configured as the authentication method for GlobalProtect, authentication on the Portal page is not successful in the browser.

**Workaround:** Use the GlobalProtect app installed on the endpoint to authenticate.

## PAN-192403

```caveat
PA-5450 firewall only
```

There is no commit warning in the web interface when configuring the management interface and logging interface in the same subnetwork. Having both interfaces in the same subnetwork can cause routing and connectivity issues.

## PAN-190735

```caveat
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
```

Certain webpages that use chunked-encoded data transfers might not load properly when analyzed by Advanced URL Filtering cloud inline categorization.

## PAN-190727

```caveat
PA-5450 firewall only
```

Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.

## PAN-190435

When you **Commit** a configuration change, the **Task Manager** commit Status goes directly from 0% to Completed and does accurately reflect the commit job progress.

## PAN-189425

```caveat
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
```

On the Panorama management server, **Export Panorama and devices config bundle** (**Panorama** > **Setup** > **Operations**) fails to export. When the export fails, you are redirected to a new window and the following error is displayed:

Failed to redirect error to /var/log/pan/appweb3-panmodule.log (Permission denied)

## PAN-189395

```caveat
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
```

Running any version of PAN-OS 10.2.1 on a PA-400 Series firewall can cause the dataplane process to restart unexpectedly and trigger a crash.

## PAN-189380

```caveat
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
```

After you successfully upgrade a PA-3000 Series firewall to PAN-OS 10.2.0 or later release and Enterprise data loss prevention (DLP) plugin 3.0.0 or later release, the first configuration push from the Panorama management server causes the firewall dataplane to crash.

**Workaround:** Restart the firewall to restore dataplane functionality.

1. [Log in to the firewall CLI](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-cli-quick-start/get-started-with-the-cli/access-the-cli).
2. Restart the firewall.
  admin> request restart system

## PAN-189111

After deleting an MP pod and it comes up, the show routing command output appears empty and traffic stops working.

## PAN-189076

On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.

**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.

## PAN-189057

```caveat
HA configuration
```

On the Panorama management server, Panorama enters a non-functional state due to php.debug.log life taking up too much space.

**Workaround:** Disable the debug flag for Panorama.

1. [Log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface).
2. In the same browser you are logged into the Panorama web interface, enter the following URL.
  https://<panorama_ip>/debug
3. Uncheck (disable) **Debug** or **Clear Debug**.
4. () Repeat this step on each Panorama high availability (HA) peer if Panorama is in a HA configuration.

## PAN-188904

```caveat
This issue is now resolved. See PAN-OS 10.2.4 Addressed Issues.
```

Certain web pages and web page contents might not properly load when cloud inline categorization is enabled on the firewall.

## PAN-188489

```caveat
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
```

On the Panorama management server, dynamic content updates are not automatically pushed to VM-Series firewalls licensed using the Panorama Software Firewall License plugin when **Automatically push content when software device registers to Panorama** (**Panorama** > **Templates** > **Add Stack**) is enabled.

## PAN-188358

After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.

## PAN-188064

```caveat
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
```

The SCP Server Profile configuration (**Devices** > **Server Profiles** > **SCP** are not automatically deleted after downgrade from PAN-OS 10.2.0 to PAN-OS 10.1 or earlier release.

## PAN-187685

On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.

**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.

## PAN-187643

If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.

**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.

## PAN-187612

On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:

- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.

**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.

admin > request plugins dlp reset

## PAN-187429

```caveat
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
```

On PA-3400 & PA-5400 series firewalls (minus the PA-5450), the CLI and SNMP MIB walk do not display the Model and Serial-number of the Fan tray and PSUs.

## PAN-187407

The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.

## PAN-187370

On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.

**Workaround**: Do not use a logical router instance with no interfaces bound to it.

## PAN-187234

```caveat
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
```

Certain web pages submitted for analysis by Advanced URL Filtering cloud inline categorization might experience high latency.

## PAN-186913

```caveat
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
```

On the Panorama management server, **Validate Device Group** (**Commit** > **Commit and Push** erroneously issues a CommitAll operation instead of a ValidateAll operation when multiple device groups are included in the push and results in no configuration validation.

**Workaround:** Validate device group configurations using one of the following methods.

- Select only one device group when you **Validate Device Group** for a **Commit and Push** to managed firewalls.
- To validate multiple device groups, select **Commit** > **Commit to Panorama** first. After the device group configuration is committed to Panorama, select **Commit** > **Push to Devices** and **Validate Device Group** to validate multiple device groups.

## PAN-186283

Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.

**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.

## PAN-186282

On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.

**Workaround:** Reboot the Panorama HA pair.

## PAN-186262

The Panorama management server in Panorama or Log Collector mode may become unresponsive as Elasticsearch accumulates internal connections related to logging processes. The chances Panorama becomes unresponsive increases the longer Panorama remains powered on.

**Workaround:** Reboot Panorama if it becomes unresponsive.

## PAN-186134

On the Panorama management server, performing a **Commit and Push** (**Commit > Commit and Push**) may intermittently not push the committed configuration changes to managed firewalls.

**Workaround:** Select **Commit > Push to Devices** to push the committed configuration changes to your managed firewalls.

## PAN-185286

```caveat
PA-5400 Series firewalls only
```

On the Panorama management server, the device health resources (**Panorama** > **Managed Devices** > **Health**) do not populate.

## PAN-184708

```caveat
Panorama managed firewalls
```

Scheduled report emails (**Monitor** > **PDF Reports** > **Email Scheduler**) are not emailed if:

- A scheduled report email contains a Report Group (**Monitor** > **PDF Reports** > **Report Group**) which includes a SaaS Application Usage report.
- A scheduled report contains only a SaaS Application Usage Report.

**Workaround:** To receive a scheduled report email for all other PDF report types:

1. Select **Monitor** > **PDF Reports** > **Report Groups** and remove all SaaS Application Usage reports from all Report Groups.
2. Select **Monitor** > **PDF Reports** > **Email Scheduler** and edit the scheduled report email that contains only a SaaS Application Usage report. For the Recurrence, select **Disable** and click **OK**.
  Repeat this step for all scheduled report emails that contain only a SaaS Application Usage report.
3. **Commit**.
  () Select **Commit** > **Commit and Push**

## PAN-184702

```caveat
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
```

On the Panorama management server, an M-700 appliance in Log Collector mode fails to connect to Panorama when added as a managed collector (**Panorama > Managed Collectors**).

**Workaround:** [Log in to the M-700 CLI](https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli.html) and [recover the Log Collector connectivity to Panorama](https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/troubleshooting/recover-managed-device-connectivity-to-panorama.html).

## PAN-184474

```caveat
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
```

When the firewall has Advanced Routing enabled, a static route stays active after the interface goes down.

**Workaround**: For firewalls that support Bidirectional Forwarding Detection (BFD), configure BFD for the static route.

## PAN-184406

Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.

**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.

## PAN-183404

Static IP addresses are not recognized when "and" operators are used with IP CIDR range.

## PAN-182734

```caveat
This issue is now resolved. See PAN-OS 10.2.5 Addressed Issues.
```

On an Advanced Routing Engine, if you change the IPSec tunnel configuration, BGP flaps.

## PAN-181933

If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.

## PAN-181823

On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.

## PAN-180661

On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays commit time out as the reason the commit failed.

## PAN-180104

When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.

**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.

## PAN-178194

```caveat
This issue is now resolved. See PAN-OS 10.2.3 Addressed Issues.
```

A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.

**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:

- Define URL exceptions for specific web sites—
  admin#set profiles url-filtering <url_filtering_profile_name> mlav-category-exception

- Configuration settings for each inline ML model—
  admin#set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled

## PAN-177455

```caveat
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues.
```

PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.

## PAN-176156

```caveat
This issue is now resolved. See PAN-OS 10.2.2 Addressed Issues
```

Executing show running resource-monitor with the ingress-backlogs option produces the following server error: Dataplane is not up or invalid target-dp(*.dp*).

## PAN-175915

When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.

## PAN-174982

In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.

## PAN-172274

When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.

**Workaround:** Issue the following command to retrieve and update the licenses: license request fetch.

## PAN-172132

```caveat
This issue is now resolved by PAN-189643. See PAN-OS 10.2.4 Addressed Issues.
```

QoS fails to run on a tunnel interface (for example, tunnel.1).

## PAN-171938

No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).

## PAN-164885

```caveat
This issue is now resolved. See PAN-OS 10.2.10 Addressed Issues.
```

On the Panorama management server, pushes to managed firewalls (**Commit** > **Push to Devices** or **Commit and Push**) may fail when an EDL (**Objects** > **External Dynamic Lists**) is configured to **Check for updates** every 5 minutes due to the commit and EDL fetch processes overlapping. This is more likely to occur when multiple EDLs are configured to check for updates every 5 minutes.
