aaron.axvig/firewallissues
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add Markdown->JSON tests

Browse Source
This commit is contained in:
aaron.axvig
2026-03-20 09:28:59 -05:00
parent 6255ecc41d
commit c16ba4bc40
9 changed files with 687 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scripts/generate-rendered-fixtures.mjs
+50
View File
@@ -0,0 +1,50 @@
/**
* Generates expected-parsed.json for each fixture directory that contains expected.md.
* Run manually: node test/generate-rendered-fixtures.mjs
*/
import { readFileSync, writeFileSync, readdirSync } from 'node:fs';
import { join } from 'node:path';
import { fileURLToPath } from 'node:url';
import { JSDOM } from 'jsdom';
const { window } = new JSDOM('<!doctype html><html><body></body></html>');
globalThis.DOMParser = window.DOMParser;
globalThis.fetch = () => Promise.resolve({
ok: true,
json: () => Promise.resolve([]),
text: () => Promise.resolve('')
});
const { parseMarkdownIssues, markdownSummaryToHtml } = await import('../web/js/issues.js');
const __dirname = fileURLToPath(new URL('.', import.meta.url));
const fixturesDir = join(__dirname, 'fixtures');
const fixtures = readdirSync(fixturesDir).filter(name => {
const contents = readdirSync(join(fixturesDir, name)).map(d => d);
return contents.includes('expected.md');
});
for (const fixtureId of fixtures) {
const fixturePath = join(fixturesDir, fixtureId);
const markdownText = readFileSync(join(fixturePath, 'expected.md'), 'utf-8');
const parsed = parseMarkdownIssues(markdownText);
const result = parsed.map(issue => ({
id: issue.id,
summary: issue.summary,
resolved: issue.resolved,
caveat: issue.caveat,
renderedHtml: markdownSummaryToHtml(issue.summary, issue.resolved, issue.caveat)
}));
writeFileSync(
join(fixturePath, 'expected-parsed.json'),
JSON.stringify(result, null, 2) + '\n',
'utf-8'
);
console.log(`Written ${fixtureId}/expected-parsed.json (${result.length} issues)`);
}
test/fixtures/PAA-25.6.2-known/expected-parsed.json
Vendored
+9
View File
@@ -0,0 +1,9 @@
[
{
"id": "PANG-9739",
"summary": "An issue exists where Prisma Access Agent portal (LDAP) authentication on Strata Cloud Manager requires the use of certificates from the **Global** configuration scope exclusively for cookie encryption and decryption operations.When configuring portal authentication for Prisma Access Agent, you must select certificates from the **Global** scope (**NGFW and Prisma Access** > **Configuration Scope** > **Global** > **Objects** > **Certificate Management**) for this purpose and must avoid using certificates that share the same name across different scopes.Specifically, if a certificate is selected from the **Global** scope for portal authentication, you must verify that no certificate with an identical name exists under the **Prisma Access** or **Access Agent** scopes, as any naming conflict can cause authentication issues. This scope restriction is necessary to prevent certificate conflicts and ensure proper cookie handling during the LDAP authentication process for Prisma Access Agent users.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>An issue exists where Prisma Access Agent portal (LDAP) authentication on Strata Cloud Manager requires the use of certificates from the <strong>Global</strong> configuration scope exclusively for cookie encryption and decryption operations.When configuring portal authentication for Prisma Access Agent, you must select certificates from the <strong>Global</strong> scope (<strong>NGFW and Prisma Access</strong> &gt; <strong>Configuration Scope</strong> &gt; <strong>Global</strong> &gt; <strong>Objects</strong> &gt; <strong>Certificate Management</strong>) for this purpose and must avoid using certificates that share the same name across different scopes.Specifically, if a certificate is selected from the <strong>Global</strong> scope for portal authentication, you must verify that no certificate with an identical name exists under the <strong>Prisma Access</strong> or <strong>Access Agent</strong> scopes, as any naming conflict can cause authentication issues. This scope restriction is necessary to prevent certificate conflicts and ensure proper cookie handling during the LDAP authentication process for Prisma Access Agent users.</p>\n"
}
]
test/fixtures/PAA-25.7.1-known/expected-parsed.json
Vendored
+37
View File
@@ -0,0 +1,37 @@
[
{
"id": "PANG-10158",
"summary": "When attempting to install Prisma Access Agent on an Ubuntu 24 virtual machine (VM) via SSH or RDP, the installation fails with an error indicating that the user environment was not preserved, even when the `sudo -E` option is used.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>When attempting to install Prisma Access Agent on an Ubuntu 24 virtual machine (VM) via SSH or RDP, the installation fails with an error indicating that the user environment was not preserved, even when the <code>sudo -E</code> option is used.</p>\n"
},
{
"id": "PANG-10342",
"summary": "An issue exists where the Prisma Access Agent on Debian Linux experiences intermittent SSL tunnel disconnection and automatic reconnection due to health keepalive timeouts. When using the agent with an SSL tunnel configuration on Debian, the tunnel repeatedly disconnects and reconnects without any manual intervention from the user. This behavior disrupts the stability of the connection, potentially affecting user productivity and network reliability.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>An issue exists where the Prisma Access Agent on Debian Linux experiences intermittent SSL tunnel disconnection and automatic reconnection due to health keepalive timeouts. When using the agent with an SSL tunnel configuration on Debian, the tunnel repeatedly disconnects and reconnects without any manual intervention from the user. This behavior disrupts the stability of the connection, potentially affecting user productivity and network reliability.</p>\n"
},
{
"id": "PANG-10309",
"summary": "An issue exists where the Prisma Access Agent on Linux fails to perform HIP updates when using the PACLI command. When administrators attempt to execute the `pacli hip update` command while the agent is connected, the operation fails because HIP updates are not supported yet.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>An issue exists where the Prisma Access Agent on Linux fails to perform HIP updates when using the PACLI command. When administrators attempt to execute the <code>pacli hip update</code> command while the agent is connected, the operation fails because HIP updates are not supported yet.</p>\n"
},
{
"id": "PANG-10271",
"summary": "When upgrading Prisma Access Agent from version 25.7.1.1 to 25.7.1.2 on a Debian ARM system, a crash file is automatically generated upon launching or using Prisma Access Agent.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>When upgrading Prisma Access Agent from version 25.7.1.1 to 25.7.1.2 on a Debian ARM system, a crash file is automatically generated upon launching or using Prisma Access Agent.</p>\n"
},
{
"id": "PANG-10019",
"summary": "After installing Prisma Access Agent 25.6.0.10 on an Arch Linux x86 system, a coredump occurs when attempting to connect to an endpoint management (EPM) system and a gateway.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>After installing Prisma Access Agent 25.6.0.10 on an Arch Linux x86 system, a coredump occurs when attempting to connect to an endpoint management (EPM) system and a gateway.</p>\n"
}
]
test/fixtures/PAA-26.1-Linux-known/expected-parsed.json
Vendored
+58
View File
@@ -0,0 +1,58 @@
[
{
"id": "PANG-11201",
"summary": "On Prisma Access Agents for Linux, when NetworkManager is configured not to manage the tunnel interface, the Prisma Access Agent connection profile becomes stuck in an \"activating\" state, resulting in a tunnel connect and disconnect loop that prevents successful establishment of the tunnel.",
"resolved": "Resolved in Prisma Access Agent 26.1.1",
"caveat": "",
"renderedHtml": "<div><strong>Resolved:</strong> Resolved in Prisma Access Agent 26.1.1</div><p>On Prisma Access Agents for Linux, when NetworkManager is configured not to manage the tunnel interface, the Prisma Access Agent connection profile becomes stuck in an \"activating\" state, resulting in a tunnel connect and disconnect loop that prevents successful establishment of the tunnel.</p>\n"
},
{
"id": "PANG-11153",
"summary": "On Linux, the Prisma Access Agent may experience recurring PASrv process crashes approximately every 20 seconds due to abnormal termination, causing the agent to become unresponsive and preventing log collection. This issue occurs primarily during agent upgrade operations.",
"resolved": "Resolved in Prisma Access Agent 26.1.1",
"caveat": "",
"renderedHtml": "<div><strong>Resolved:</strong> Resolved in Prisma Access Agent 26.1.1</div><p>On Linux, the Prisma Access Agent may experience recurring PASrv process crashes approximately every 20 seconds due to abnormal termination, causing the agent to become unresponsive and preventing log collection. This issue occurs primarily during agent upgrade operations.</p>\n"
},
{
"id": "PANG-10947",
"summary": "When Prisma Access Agent is configured in on-demand mode on Arch Linux and the network connection is interrupted and then restored, the agent fails to automatically reconnect to the gateway. As a result, the agent remains in a disconnected state.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>When Prisma Access Agent is configured in on-demand mode on Arch Linux and the network connection is interrupted and then restored, the agent fails to automatically reconnect to the gateway. As a result, the agent remains in a disconnected state.</p>\n"
},
{
"id": "PANG-10865",
"summary": "On Prisma Access Agent for Linux systems, the Prisma Access Agent user interface exhibits minor cosmetic and usability inconsistencies. The Location list lacks a line separator between entries and is not sorted alphabetically, with the exception of the \"Best Location\" option.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>On Prisma Access Agent for Linux systems, the Prisma Access Agent user interface exhibits minor cosmetic and usability inconsistencies. The Location list lacks a line separator between entries and is not sorted alphabetically, with the exception of the \"Best Location\" option.</p>\n"
},
{
"id": "PANG-10801",
"summary": "During a Host Information Profile (HIP) check on Prisma Access Agent for Linux, the system incorrectly validates certificates based solely on the issuer's Common Name (CN). This results in expired or revoked certificates being considered valid if their issuer's CN matches the configured criteria, potentially allowing non-compliant endpoints to pass HIP checks.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>During a Host Information Profile (HIP) check on Prisma Access Agent for Linux, the system incorrectly validates certificates based solely on the issuer's Common Name (CN). This results in expired or revoked certificates being considered valid if their issuer's CN matches the configured criteria, potentially allowing non-compliant endpoints to pass HIP checks.</p>\n"
},
{
"id": "PANG-10668",
"summary": "After upgrading to Prisma Access Agent version 26.1.0.25 on Arch Linux with KDE Plasma desktop environments, the settings page in the Prisma Access Agent app might appear partially blank when the operating system's dark theme is enabled. This prevents the display of relevant information on the settings page.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>After upgrading to Prisma Access Agent version 26.1.0.25 on Arch Linux with KDE Plasma desktop environments, the settings page in the Prisma Access Agent app might appear partially blank when the operating system's dark theme is enabled. This prevents the display of relevant information on the settings page.</p>\n"
},
{
"id": "PANG-9501",
"summary": "When using Prisma Access Agent on a system running Fedora 42 (GNOME), running the `pacli traffic log <n>` command does not show the log details.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>When using Prisma Access Agent on a system running Fedora 42 (GNOME), running the <code>pacli traffic log &lt;n&gt;</code> command does not show the log details.</p>\n"
},
{
"id": "PANG-9196",
"summary": "When Prisma Access Agent is installed on a Linux virtual machine (VM) running on an ESXi host, and the VM undergoes network changes (such as connecting or disconnecting from gateways) or experiences a sleep/wake cycle, the entire VM and the ESXi host might become unresponsive. Access to the ESXi host is lost, and the system hangs for approximately 5 minutes before access is regained.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>When Prisma Access Agent is installed on a Linux virtual machine (VM) running on an ESXi host, and the VM undergoes network changes (such as connecting or disconnecting from gateways) or experiences a sleep/wake cycle, the entire VM and the ESXi host might become unresponsive. Access to the ESXi host is lost, and the system hangs for approximately 5 minutes before access is regained.</p>\n"
}
]
test/fixtures/PAA-26.1.1-known/expected-parsed.json
Vendored
+51
View File
@@ -0,0 +1,51 @@
[
{
"id": "PANG-11346",
"summary": "When Prisma Access Agent is connected on a Linux host system, Docker containers running on that host are unable to perform network communication using `curl` commands. Attempts to send `curl` traffic from inside a container result in a \"Network is unreachable\" error, even though the host system itself retains full network connectivity.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>When Prisma Access Agent is connected on a Linux host system, Docker containers running on that host are unable to perform network communication using <code>curl</code> commands. Attempts to send <code>curl</code> traffic from inside a container result in a \"Network is unreachable\" error, even though the host system itself retains full network connectivity.</p>\n"
},
{
"id": "PANG-11254",
"summary": "When the Dynamic Privilege Access-enabled Prisma Access Agent is in the notify-before-re-authentication period displaying a countdown timer banner and **Aggressive Authentication** is not enabled, switching projects in the Prisma Access Agent app triggers re-authentication and updates the User Refresh Token expiry time. However, the countdown timer banner continues to display the previous timer value until it expires, despite the successful re-authentication. Once the original timer completes, the banner disappears.",
"resolved": "Fixed in Prisma Access Agent 26.1.2 (PANG-11311)",
"caveat": "",
"renderedHtml": "<div><strong>Resolved:</strong> Fixed in Prisma Access Agent 26.1.2 (PANG-11311)</div><p>When the Dynamic Privilege Access-enabled Prisma Access Agent is in the notify-before-re-authentication period displaying a countdown timer banner and <strong>Aggressive Authentication</strong> is not enabled, switching projects in the Prisma Access Agent app triggers re-authentication and updates the User Refresh Token expiry time. However, the countdown timer banner continues to display the previous timer value until it expires, despite the successful re-authentication. Once the original timer completes, the banner disappears.</p>\n"
},
{
"id": "PANG-11199",
"summary": "For Panorama Managed NGFW deployments, Prisma Access Agent ignores the IPv6 address field in external gateway configurations received from Endpoint Manager get-config responses. When an IPv6 address is configured for an external gateway in the Edit External Gateway window in Strata Cloud Manager, Prisma Access Agent fails to process it. For dual-stack gateways configured with both IPv4 and IPv6 addresses, only the IPv4 address is recognized and the IPv6 address is completely ignored. For IPv6-only gateways, Prisma Access Agent throws an invalid configuration error and the gateway cannot be established.**Workaround**: Configure the gateway using a Fully Qualified Domain Name (FQDN) instead of an IPv6 address.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>For Panorama Managed NGFW deployments, Prisma Access Agent ignores the IPv6 address field in external gateway configurations received from Endpoint Manager get-config responses. When an IPv6 address is configured for an external gateway in the Edit External Gateway window in Strata Cloud Manager, Prisma Access Agent fails to process it. For dual-stack gateways configured with both IPv4 and IPv6 addresses, only the IPv4 address is recognized and the IPv6 address is completely ignored. For IPv6-only gateways, Prisma Access Agent throws an invalid configuration error and the gateway cannot be established.<strong>Workaround</strong>: Configure the gateway using a Fully Qualified Domain Name (FQDN) instead of an IPv6 address.</p>\n"
},
{
"id": "PANG-11178",
"summary": "When Prisma Access Agent is configured with portal authentication and the **Save User Credentials** option disabled, and the user clicks on the re-authentication banner in the agent app when the session is about to expire, an \"Authentication Failed\" error notification is displayed instead of prompting the user to enter their credentials. The user is not given the opportunity to re-authenticate as expected.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>When Prisma Access Agent is configured with portal authentication and the <strong>Save User Credentials</strong> option disabled, and the user clicks on the re-authentication banner in the agent app when the session is about to expire, an \"Authentication Failed\" error notification is displayed instead of prompting the user to enter their credentials. The user is not given the opportunity to re-authenticate as expected.</p>\n"
},
{
"id": "PANG-11141",
"summary": "When Prisma Access Agent is configured with client certificate authentication or portal authentication, the User Refresh Token does not automatically refresh at the end of its expiry period. The agent fails to attempt token renewal, which can result in authentication expiration and loss of user access once the User Refresh Token expires.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>When Prisma Access Agent is configured with client certificate authentication or portal authentication, the User Refresh Token does not automatically refresh at the end of its expiry period. The agent fails to attempt token renewal, which can result in authentication expiration and loss of user access once the User Refresh Token expires.</p>\n"
},
{
"id": "PANG-11103",
"summary": "When Prisma Access agent is actively connected to a gateway and the IPv6 pool is disabled on the tenant, the agent retains a stale IPv6 tunnel IP address. This stale IP persists on the specific gateway that was connected during the configuration change, even after the agent signs out and signs back in. The gateway address and IPv4 tunnel IP correctly update to reflect the new configuration, but the IPv6 tunnel field incorrectly displays the old IPv6 pool IP instead of \"N/A\". Gateways that were not actively connected during the configuration change correctly show no IPv6 tunnel IP.Users may incorrectly believe they still have IPv6 connectivity when they do not. This stale data complicates troubleshooting and causes automated tests to receive incorrect state information.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>When Prisma Access agent is actively connected to a gateway and the IPv6 pool is disabled on the tenant, the agent retains a stale IPv6 tunnel IP address. This stale IP persists on the specific gateway that was connected during the configuration change, even after the agent signs out and signs back in. The gateway address and IPv4 tunnel IP correctly update to reflect the new configuration, but the IPv6 tunnel field incorrectly displays the old IPv6 pool IP instead of \"N/A\". Gateways that were not actively connected during the configuration change correctly show no IPv6 tunnel IP.Users may incorrectly believe they still have IPv6 connectivity when they do not. This stale data complicates troubleshooting and causes automated tests to receive incorrect state information.</p>\n"
},
{
"id": "PANG-10925",
"summary": "When a device with Prisma Access Agent configured for Dynamic Privilege Access wakes up from sleep mode, the agent reconnects without enforcing re-authentication, even when **Aggressive Authentication** is enabled. The agent establishes connectivity without requiring the user to provide credentials again, bypassing the expected authentication enforcement.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>When a device with Prisma Access Agent configured for Dynamic Privilege Access wakes up from sleep mode, the agent reconnects without enforcing re-authentication, even when <strong>Aggressive Authentication</strong> is enabled. The agent establishes connectivity without requiring the user to provide credentials again, bypassing the expected authentication enforcement.</p>\n"
}
]
test/fixtures/PAN-OS-11.0.6-known/expected-parsed.json
Vendored
+338
View File
@@ -0,0 +1,338 @@
[
{
"id": "WF500-5632",
"summary": "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.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>The number of registered WildFire appliances reported in Panorama (<strong>Panorama</strong> &gt; <strong>Managed WildFire Appliances</strong> &gt; <strong>Firewalls Connected</strong> &gt; <strong>View</strong>) does not accurately reflect the current status of connected WildFire appliances.</p>\n"
},
{
"id": "PAN-260851",
"summary": "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.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (<strong>Objects</strong> &gt; <strong>Applications</strong>) tag.</p>\n"
},
{
"id": "PAN-250062",
"summary": "Device telemetry might fail at configured intervals due to bundle generation issues.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Device telemetry might fail at configured intervals due to bundle generation issues.</p>\n"
},
{
"id": "PAN-234015",
"summary": "The X-Forwarded-For (XFF) value is not displayed in traffic logs.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>The X-Forwarded-For (XFF) value is not displayed in traffic logs.</p>\n"
},
{
"id": "PAN-252744",
"summary": "After upgrading PA-3200 Series, PA-5200 Series, or PA-7000 Series firewalls that are equipped with OCTEON 7x00 dataplane chips to PAN-OS 11.0.4 or 11.0.4-h1, the firewall might see continuous crashes, reboot repeatedly, and/or go into a non-functional state.**Workaround:** If you have already upgraded to one of those releases, downgrade to an earlier release or upgrade to PAN-OS 11.0.4-h2.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>After upgrading PA-3200 Series, PA-5200 Series, or PA-7000 Series firewalls that are equipped with OCTEON 7x00 dataplane chips to PAN-OS 11.0.4 or 11.0.4-h1, the firewall might see continuous crashes, reboot repeatedly, and/or go into a non-functional state.<strong>Workaround:</strong> If you have already upgraded to one of those releases, downgrade to an earlier release or upgrade to PAN-OS 11.0.4-h2.</p>\n"
},
{
"id": "PAN-241041",
"summary": "On the Panorama management server exporting template or template stack variables (**Panorama** > **Templates**) in CSV format results in an empty CSV file.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>On the Panorama management server exporting template or template stack variables (<strong>Panorama</strong> &gt; <strong>Templates</strong>) in CSV format results in an empty CSV file.</p>\n"
},
{
"id": "PAN-234929",
"summary": "The tabs in the **ACC**, such as **Network Activity**, **Threat Activity**, and **Blocked Activity**, may not display any data when you apply a Time filter for the Last 15 minutes, Last Hour, Last 6 Hours, or Last 12 Hours. With the Last 24 Hours filter, the data displayed may not be accurate. Additionally, reports run against summary logs may not display accurate results.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>The tabs in the <strong>ACC</strong>, such as <strong>Network Activity</strong>, <strong>Threat Activity</strong>, and <strong>Blocked Activity</strong>, may not display any data when you apply a Time filter for the Last 15 minutes, Last Hour, Last 6 Hours, or Last 12 Hours. With the Last 24 Hours filter, the data displayed may not be accurate. Additionally, reports run against summary logs may not display accurate results.</p>\n"
},
{
"id": "PAN-225886",
"summary": "If you enable explicit proxy mode for the web proxy, intermittent errors and unexpected TCP reconnections may occur.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>If you enable explicit proxy mode for the web proxy, intermittent errors and unexpected TCP reconnections may occur.</p>\n"
},
{
"id": "PAN-233677",
"summary": "By enabling [Lockless QoS feature](https://docs.paloaltonetworks.com/pan-os/11-0/pan-os-admin/quality-of-service/configure-lockless-qos.html), a slight degradation in App-ID and Threat performance is expected.",
"resolved": "",
"caveat": "PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, PA-5430, and PA-5440 firewalls",
"renderedHtml": "<div><em>Caveat: PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, PA-5430, and PA-5440 firewalls</em></div><p>By enabling <a href=\"https://docs.paloaltonetworks.com/pan-os/11-0/pan-os-admin/quality-of-service/configure-lockless-qos.html\">Lockless QoS feature</a>, a slight degradation in App-ID and Threat performance is expected.</p>\n"
},
{
"id": "PAN-222586",
"summary": "On PA-5410, PA-5420, PA-5430, and PA-5440 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.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>On PA-5410, PA-5420, PA-5430, and PA-5440 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (<strong>Device</strong> &gt; <strong>Log Settings</strong>) are not displayed and cannot be configured.</p>\n"
},
{
"id": "PAN-220176",
"summary": "System process crashes might occur with VoIP traffic when NAT is enabled with Persistent Dynamic IP and Port settings.",
"resolved": "",
"caveat": "PAN-OS 11.0.1-h2 hotfix",
"renderedHtml": "<div><em>Caveat: PAN-OS 11.0.1-h2 hotfix</em></div><p>System process crashes might occur with VoIP traffic when NAT is enabled with Persistent Dynamic IP and Port settings.</p>\n"
},
{
"id": "PAN-216314",
"summary": "Upon upgrade or downgrade to or from PAN-OS 10.1.9 or 10.1.9-h1, offloaded application traffic sessions may disconnect after a period of time even if a session is active. The disconnect occurs after the application's default session timeout value is exceeded. This behavior affects only PAN-OS 10.1.9 and 10.1.9-h1. If you are on PAN-OS 10.1.9 and 10.1.9-h1, please use the following workaround. If you have already upgraded or downgraded to another PAN-OS version, use the following workaround in that version.**Workaround:** Run the CLI command `debug dataplane internal pdt fe100 csr wr_sem_ctrl_ctr_scan_dis value 0` to set the value to zero (0).",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Upon upgrade or downgrade to or from PAN-OS 10.1.9 or 10.1.9-h1, offloaded application traffic sessions may disconnect after a period of time even if a session is active. The disconnect occurs after the application's default session timeout value is exceeded. This behavior affects only PAN-OS 10.1.9 and 10.1.9-h1. If you are on PAN-OS 10.1.9 and 10.1.9-h1, please use the following workaround. If you have already upgraded or downgraded to another PAN-OS version, use the following workaround in that version.<strong>Workaround:</strong> Run the CLI command <code>debug dataplane internal pdt fe100 csr wr_sem_ctrl_ctr_scan_dis value 0</code> to set the value to zero (0).</p>\n"
},
{
"id": "PAN-216214",
"summary": "For Panorama-managed firewalls in an Active/Active High Availability (HA) configuration where you configure the firewall HA settings (**Device** > **High Availability**) in a template or template stack (**Panorama** > **Templates**), performing a local commit on one of the HA firewalls triggers an HA config sync on the peer firewall. This causes the HA peer configuration to go `Out of Sync`.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>For Panorama-managed firewalls in an Active/Active High Availability (HA) configuration where you configure the firewall HA settings (<strong>Device</strong> &gt; <strong>High Availability</strong>) in a template or template stack (<strong>Panorama</strong> &gt; <strong>Templates</strong>), performing a local commit on one of the HA firewalls triggers an HA config sync on the peer firewall. This causes the HA peer configuration to go <code>Out of Sync</code>.</p>\n"
},
{
"id": "PAN-213746",
"summary": "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.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>On the Panorama management server, the <strong>Hostkey</strong> displayed as <code>undefined undefined</code> if you override an SSH Service Profile (<strong>Device</strong> &gt; <strong>Certificate Management</strong> &gt; <strong>SSH Service Profile</strong>) Hostkey configured in a Template from the Template Stack.</p>\n"
},
{
"id": "PAN-213119",
"summary": "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`",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (<strong>Monitor</strong> &gt; <strong>Block IP</strong>):<code>show -&gt; dis-block-table is unexpected</code></p>\n"
},
{
"id": "PAN-212978",
"summary": "The Palo Alto Networks firewall stops responding when executing an SD-WAN debug operational CLI command.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>The Palo Alto Networks firewall stops responding when executing an SD-WAN debug operational CLI command.</p>\n"
},
{
"id": "PAN-212889",
"summary": "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.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (<strong>Monitor</strong> &gt; <strong>App Scope</strong> &gt; <strong>Threat Monitor</strong>) and <strong>ACC</strong>. This results in the ACC displaying <code>no data to display</code> 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.</p>\n"
},
{
"id": "PAN-211531",
"summary": "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**).",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>On the Panorama management server, admins can still perform a selective push to managed firewalls when <strong>Push All Changes</strong> and <strong>Push for Other Admins</strong> are disabled in the admin role profile (<strong>Panorama</strong> &gt; <strong>Admin Roles</strong>).</p>\n"
},
{
"id": "PAN-207770",
"summary": "Data filtering logs (**Monitor** > **Logs** > **Data Filtering**) incorrectly display the traffic Direction as `server-to-client` instead of `client-to-server` for upload traffic that matches Enterprise data loss prevention (DLP) data patterns (**Objects** > **DLP** > **Data Filtering Patterns**) in an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles**).",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Data filtering logs (<strong>Monitor</strong> &gt; <strong>Logs</strong> &gt; <strong>Data Filtering</strong>) incorrectly display the traffic Direction as <code>server-to-client</code> instead of <code>client-to-server</code> for upload traffic that matches Enterprise data loss prevention (DLP) data patterns (<strong>Objects</strong> &gt; <strong>DLP</strong> &gt; <strong>Data Filtering Patterns</strong>) in an Enterprise DLP data filtering profile (<strong>Objects</strong> &gt; <strong>DLP</strong> &gt; <strong>Data Filtering Profiles</strong>).</p>\n"
},
{
"id": "PAN-207733",
"summary": "When a DHCPv6 client is configured on HA Active/Passive firewalls, if the DHCPv6 server goes down, after the lease time expires, the DHCPv6 client should enter SOLICIT state on both the Active and Passive firewalls. Instead, the client is stuck in BOUND state with an IPv6 address having lease time 0 on the Passive firewall.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>When a DHCPv6 client is configured on HA Active/Passive firewalls, if the DHCPv6 server goes down, after the lease time expires, the DHCPv6 client should enter SOLICIT state on both the Active and Passive firewalls. Instead, the client is stuck in BOUND state with an IPv6 address having lease time 0 on the Passive firewall.</p>\n"
},
{
"id": "PAN-207616",
"summary": "On the Panorama management server, after selecting managed firewalls and creating a new **Tag** (**Panorama** > **Managed Devices** > **Summary**) the managed firewalls are automatically unselected and any new tag created is applied to the managed firewalls for which you initially created the new tag.**Workaround:** Select and then unselect the managed firewalls for which you created a new tag.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>On the Panorama management server, after selecting managed firewalls and creating a new <strong>Tag</strong> (<strong>Panorama</strong> &gt; <strong>Managed Devices</strong> &gt; <strong>Summary</strong>) the managed firewalls are automatically unselected and any new tag created is applied to the managed firewalls for which you initially created the new tag.<strong>Workaround:</strong> Select and then unselect the managed firewalls for which you created a new tag.</p>\n"
},
{
"id": "PAN-207611",
"summary": "When a DHCPv6 client is configured on HA Active/Passive firewalls, the Passive firewall sometimes crashes.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>When a DHCPv6 client is configured on HA Active/Passive firewalls, the Passive firewall sometimes crashes.</p>\n"
},
{
"id": "PAN-207442",
"summary": "For M-700 appliances in an active/passive high availability (**Panorama** > **High Availability**) configuration, the `active-primary` HA peer configuration sync to the `secondary-passive` HA peer may fail. When the config sync fails, the job Results is `Successful` (**Tasks**), however the sync status on the **Dashboard** displays as `Out of Sync` for both HA peers.**Workaround**: Perform a local commit on the `active-primary` HA peer and then synchronize the HA configuration.1. [Log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/11-0/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface) of the `active-primary` HA peer.\n2. Select **Commit** and **Commit to Panorama**.\n3. In the `active-primary` HA peer **Dashboard**, click **Sync to Peer** in the High Availability widget.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>For M-700 appliances in an active/passive high availability (<strong>Panorama</strong> &gt; <strong>High Availability</strong>) configuration, the <code>active-primary</code> HA peer configuration sync to the <code>secondary-passive</code> HA peer may fail. When the config sync fails, the job Results is <code>Successful</code> (<strong>Tasks</strong>), however the sync status on the <strong>Dashboard</strong> displays as <code>Out of Sync</code> for both HA peers.<strong>Workaround</strong>: Perform a local commit on the <code>active-primary</code> HA peer and then synchronize the HA configuration.1. <a href=\"https://docs.paloaltonetworks.com/panorama/11-0/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface\">Log in to the Panorama web interface</a> of the <code>active-primary</code> HA peer.\n2. Select <strong>Commit</strong> and <strong>Commit to Panorama</strong>.\n3. In the <code>active-primary</code> HA peer <strong>Dashboard</strong>, click <strong>Sync to Peer</strong> in the High Availability widget.</p>\n"
},
{
"id": "PAN-207040",
"summary": "If you disable Advanced Routing, remove logical routers, and downgrade from PAN-OS 11.0.0 to a PAN-OS 10.2.x or 10.1.x release, subsequent commits fail and SD-WAN devices on Panorama have no Virtual Router name.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>If you disable Advanced Routing, remove logical routers, and downgrade from PAN-OS 11.0.0 to a PAN-OS 10.2.x or 10.1.x release, subsequent commits fail and SD-WAN devices on Panorama have no Virtual Router name.</p>\n"
},
{
"id": "PAN-206913",
"summary": "When a DHCPv6 client is configured on HA Active/Passive firewalls, releasing the IPv6 address from the client (using Release in the UI or using the `request dhcp client ipv6 release all` CLI command) releases the IPv6 address from the Active firewall, but not the Passive firewall.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>When a DHCPv6 client is configured on HA Active/Passive firewalls, releasing the IPv6 address from the client (using Release in the UI or using the <code>request dhcp client ipv6 release all</code> CLI command) releases the IPv6 address from the Active firewall, but not the Passive firewall.</p>\n"
},
{
"id": "PAN-206909",
"summary": "The Dedicated Log Collector is unable to reconnect to the Panorama management server if the `configd` process crashes. This results in the Dedicated Log Collector losing connectivity to Panorama despite the managed collector connection `Status` (**Panorama** > **Managed Collector**) displaying `connected` and the managed colletor `Health` status displaying as healthy.This results in the local Panorama config and system logs not being forwarded to the Dedicated Log Collector. Firewall log forwarding to the disconnected Dedicated Log Collector is not impacted.**Workaround:** Restart the `mgmtsrvr` process on the Dedicated Log Collector.1. [Log in to the Dedicated Log Collector CLI](https://docs.paloaltonetworks.com/panorama/11-0/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli).\n2. Confirm the Dedicated Log Collector is disconnected from Panorama.\n `admin>``show panorama-status`\n Verify the `Connected` status is `no`.\n3. Restart the `mgmtsrvr` process.\n `admin>``debug software restart process management-server`",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>The Dedicated Log Collector is unable to reconnect to the Panorama management server if the <code>configd</code> process crashes. This results in the Dedicated Log Collector losing connectivity to Panorama despite the managed collector connection <code>Status</code> (<strong>Panorama</strong> &gt; <strong>Managed Collector</strong>) displaying <code>connected</code> and the managed colletor <code>Health</code> status displaying as healthy.This results in the local Panorama config and system logs not being forwarded to the Dedicated Log Collector. Firewall log forwarding to the disconnected Dedicated Log Collector is not impacted.<strong>Workaround:</strong> Restart the <code>mgmtsrvr</code> process on the Dedicated Log Collector.1. <a href=\"https://docs.paloaltonetworks.com/panorama/11-0/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli\">Log in to the Dedicated Log Collector CLI</a>.\n2. Confirm the Dedicated Log Collector is disconnected from Panorama.\n <code>admin&gt;``show panorama-status</code>\n Verify the <code>Connected</code> status is <code>no</code>.\n3. Restart the <code>mgmtsrvr</code> process.\n <code>admin&gt;``debug software restart process management-server</code></p>\n"
},
{
"id": "PAN-206416",
"summary": "On the Panorama management server, no data filtering log (**Monitor** > **Logs** > **Data Filtering**) is generated when the managed firewall loses connectivity to the following cloud services, and as a result fails to forward matched traffic for inspection.- DLP cloud service\n- Advanced Threat Protection inline cloud analysis service\n- Advanced URL Filtering cloud service",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>On the Panorama management server, no data filtering log (<strong>Monitor</strong> &gt; <strong>Logs</strong> &gt; <strong>Data Filtering</strong>) is generated when the managed firewall loses connectivity to the following cloud services, and as a result fails to forward matched traffic for inspection.- DLP cloud service</p>\n<ul>\n<li>Advanced Threat Protection inline cloud analysis service</li>\n<li>Advanced URL Filtering cloud service</li>\n</ul>\n"
},
{
"id": "PAN-206315",
"summary": "In an active/passive high availability (HA) configuration, the `show session info` CLI command shows that the passive firewall has packet rate and throughput values. The packet rate and throughput of the passive firewall should be zero since it is not processing traffic.",
"resolved": "",
"caveat": "PA-1420 firewall only",
"renderedHtml": "<div><em>Caveat: PA-1420 firewall only</em></div><p>In an active/passive high availability (HA) configuration, the <code>show session info</code> CLI command shows that the passive firewall has packet rate and throughput values. The packet rate and throughput of the passive firewall should be zero since it is not processing traffic.</p>\n"
},
{
"id": "PAN-205009",
"summary": "In an active/passive high availability (HA) configuration, the `show interface all`, `show-high availability interface ha2`, and `show high-availability all` CLI commands display the HSCI port state as unknown on both the active and passive firewalls.",
"resolved": "",
"caveat": "PA-1420 firewall only",
"renderedHtml": "<div><em>Caveat: PA-1420 firewall only</em></div><p>In an active/passive high availability (HA) configuration, the <code>show interface all</code>, <code>show-high availability interface ha2</code>, and <code>show high-availability all</code> CLI commands display the HSCI port state as unknown on both the active and passive firewalls.</p>\n"
},
{
"id": "PAN-204689",
"summary": "Upon upgrade to PAN-OS 11.0.1, the following GlobalProtect settings do not work:- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**\n- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**\n- **Allow User to Uninstall GlobalProtect App** > **Allow with Password**",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Upon upgrade to PAN-OS 11.0.1, the following GlobalProtect settings do not work:- <strong>Allow user to disconnect GlobalProtect App</strong> &gt; <strong>Allow with Passcode</strong></p>\n<ul>\n<li><strong>Allow user to Disable GlobalProtect App</strong> &gt; <strong>Allow with Passcode</strong></li>\n<li><strong>Allow User to Uninstall GlobalProtect App</strong> &gt; <strong>Allow with Password</strong></li>\n</ul>\n"
},
{
"id": "PAN-201910",
"summary": "PAN-OS security profiles might consume a large amount of memory depending on the profile configuration and quantity. In some cases, this might reduce the number of supported security profiles below the stated maximum for a given platform.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>PAN-OS security profiles might consume a large amount of memory depending on the profile configuration and quantity. In some cases, this might reduce the number of supported security profiles below the stated maximum for a given platform.</p>\n"
},
{
"id": "PAN-197588",
"summary": "The PAN-OS ACC (Application Command Center) does not display a widget detailing statistics and data associated with vulnerability exploits that have been detected using inline cloud analysis.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>The PAN-OS ACC (Application Command Center) does not display a widget detailing statistics and data associated with vulnerability exploits that have been detected using inline cloud analysis.</p>\n"
},
{
"id": "PAN-197419",
"summary": "In **Network** > **Interface** > **Ethernet**, the power over Ethernet (PoE) ports do not display a **Tag** value.",
"resolved": "",
"caveat": "PA-1400 Series firewalls only",
"renderedHtml": "<div><em>Caveat: PA-1400 Series firewalls only</em></div><p>In <strong>Network</strong> &gt; <strong>Interface</strong> &gt; <strong>Ethernet</strong>, the power over Ethernet (PoE) ports do not display a <strong>Tag</strong> value.</p>\n"
},
{
"id": "PAN-197097",
"summary": "Large Scale VPN (LSVPN) does not support IPv6 addresses on the satellite firewall.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Large Scale VPN (LSVPN) does not support IPv6 addresses on the satellite firewall.</p>\n"
},
{
"id": "PAN-196758",
"summary": "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**).",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>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 <strong>Preview Changes</strong> (<strong>Commit</strong> &gt; <strong>Push to Devices</strong> &gt; <strong>Edit Selections</strong> or <strong>Commit</strong> &gt; <strong>Commit and Push</strong> &gt; <strong>Edit Selections</strong>).</p>\n"
},
{
"id": "PAN-195968",
"summary": "When using the CLI to configure power over Ethernet (PoE) on a non-PoE port, the CLI prints an error depending on whether an interface type was selected on the non-PoE port or not. If an interface type, such as tap, Layer 2, or virtual wire, was selected before PoE was configured, the error message will not include the interface name (eg. ethernet1/4). If an interface type was not selected before PoE was configured, the error message will include the interface name.",
"resolved": "",
"caveat": "PA-1400 Series firewalls only",
"renderedHtml": "<div><em>Caveat: PA-1400 Series firewalls only</em></div><p>When using the CLI to configure power over Ethernet (PoE) on a non-PoE port, the CLI prints an error depending on whether an interface type was selected on the non-PoE port or not. If an interface type, such as tap, Layer 2, or virtual wire, was selected before PoE was configured, the error message will not include the interface name (eg. ethernet1/4). If an interface type was not selected before PoE was configured, the error message will include the interface name.</p>\n"
},
{
"id": "PAN-195342",
"summary": "On the Panorama management server, Context Switch fails when you try to Context Switch from a managed firewall running PAN-OS 10.1.7 or earlier release back to Panorama and the following error is displayed:`Could not find start token '@start@'`",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>On the Panorama management server, Context Switch fails when you try to Context Switch from a managed firewall running PAN-OS 10.1.7 or earlier release back to Panorama and the following error is displayed:<code>Could not find start token '@start@'</code></p>\n"
},
{
"id": "PAN-194978",
"summary": "In **Network** > **Interface** > **Ethernet**, hovering the mouse over a power over Ethernet (PoE) **Link State** icon does not display link speed and link duplex details.",
"resolved": "",
"caveat": "PA-1400 Series firewalls only",
"renderedHtml": "<div><em>Caveat: PA-1400 Series firewalls only</em></div><p>In <strong>Network</strong> &gt; <strong>Interface</strong> &gt; <strong>Ethernet</strong>, hovering the mouse over a power over Ethernet (PoE) <strong>Link State</strong> icon does not display link speed and link duplex details.</p>\n"
},
{
"id": "PAN-194424",
"summary": "Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.**Workaround:** Restart the log receiver service by running the following CLI command:`debug software restart process log-receiver`",
"resolved": "",
"caveat": "PA-5450 firewall only",
"renderedHtml": "<div><em>Caveat: PA-5450 firewall only</em></div><p>Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.<strong>Workaround:</strong> Restart the log receiver service by running the following CLI command:<code>debug software restart process log-receiver</code></p>\n"
},
{
"id": "PAN-187685",
"summary": "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**.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>On the Panorama management server, the Template Status displays no synchronization status (<strong>Panorama</strong> &gt; <strong>Managed Devices</strong> &gt; <strong>Summary</strong>) after a bootstrapped firewall is successfully added to Panorama.<strong>Workaround:</strong> After the bootstrapped firewall is successfully added to Panorama, <a href=\"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\">log in to the Panorama web interface</a> and select <strong>Commit</strong> &gt; <strong>Push to Devices</strong>.</p>\n"
},
{
"id": "PAN-187407",
"summary": "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.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>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 <strong>Hold client request for category lookup</strong>and the action set to <strong>Reset-Both</strong> and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.</p>\n"
},
{
"id": "PAN-186283",
"summary": "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.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.<strong>Workaround</strong>: Use <strong>Commit</strong> &gt; <strong>Push to Devices</strong> to synchronize the templates.</p>\n"
},
{
"id": "PAN-184708",
"summary": "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.\n- 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.\n2. 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**.\n Repeat this step for all scheduled report emails that contain only a SaaS Application Usage report.\n3. **Commit**.\n () Select **Commit** > **Commit and Push**",
"resolved": "",
"caveat": "Panorama managed firewalls",
"renderedHtml": "<div><em>Caveat: Panorama managed firewalls</em></div><p>Scheduled report emails (<strong>Monitor</strong> &gt; <strong>PDF Reports</strong> &gt; <strong>Email Scheduler</strong>) are not emailed if:- A scheduled report email contains a Report Group (<strong>Monitor</strong> &gt; <strong>PDF Reports</strong> &gt; <strong>Report Group</strong>) which includes a SaaS Application Usage report.</p>\n<ul>\n<li>A scheduled report contains only a SaaS Application Usage Report.<strong>Workaround:</strong> To receive a scheduled report email for all other PDF report types:1. Select <strong>Monitor</strong> &gt; <strong>PDF Reports</strong> &gt; <strong>Report Groups</strong> and remove all SaaS Application Usage reports from all Report Groups.</li>\n</ul>\n<ol start=\"2\">\n<li>Select <strong>Monitor</strong> &gt; <strong>PDF Reports</strong> &gt; <strong>Email Scheduler</strong> and edit the scheduled report email that contains only a SaaS Application Usage report. For the Recurrence, select <strong>Disable</strong> and click <strong>OK</strong>.\n Repeat this step for all scheduled report emails that contain only a SaaS Application Usage report.</li>\n<li><strong>Commit</strong>.\n () Select <strong>Commit</strong> &gt; <strong>Commit and Push</strong></li>\n</ol>\n"
},
{
"id": "PAN-184406",
"summary": "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.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.<strong>Workaround:</strong> Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.</p>\n"
},
{
"id": "PAN-183404",
"summary": "Static IP addresses are not recognized when \"and\" operators are used with IP CIDR range.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Static IP addresses are not recognized when \"and\" operators are used with IP CIDR range.</p>\n"
},
{
"id": "PAN-181933",
"summary": "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.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>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.</p>\n"
},
{
"id": "PAN-171938",
"summary": "No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>No results are displayed when you <strong>Show Application Filter</strong> for a Security policy rule (<strong>Policies</strong> &gt; <strong>Security</strong> &gt; <strong>Application</strong> &gt; <strong>Value</strong> &gt; <strong>Show Application Filter</strong>).</p>\n"
},
{
"id": "PAN-164885",
"summary": "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.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>On the Panorama management server, pushes to managed firewalls (<strong>Commit</strong> &gt; <strong>Push to Devices</strong> or <strong>Commit and Push</strong>) may fail when an EDL (<strong>Objects</strong> &gt; <strong>External Dynamic Lists</strong>) is configured to <strong>Check for updates</strong> 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.</p>\n"
}
]
test/fixtures/PAN-OS-11.1.13-h3-addressed/expected-parsed.json
Vendored
+93
View File
@@ -0,0 +1,93 @@
[
{
"id": "PAN-316911",
"summary": "Fixed an issue where a newly bootstrapped firewall required a management server restart, relicensing, or license push from Panorama to invoke the device certificate.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Fixed an issue where a newly bootstrapped firewall required a management server restart, relicensing, or license push from Panorama to invoke the device certificate.</p>\n"
},
{
"id": "PAN-315176",
"summary": "Added an enable and disable CLI command to address an issue where the firewall experienced increased packet drops and slower performance after an upgrade due to high burst traffic.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Added an enable and disable CLI command to address an issue where the firewall experienced increased packet drops and slower performance after an upgrade due to high burst traffic.</p>\n"
},
{
"id": "PAN-314061",
"summary": "Fixed an issue where traffic was disrupted during IPSec rekey operations due to a 2 second delay in sending the DELETE message for the previous Security Association (SA) to the peer gateway after a new SA was negotiated.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Fixed an issue where traffic was disrupted during IPSec rekey operations due to a 2 second delay in sending the DELETE message for the previous Security Association (SA) to the peer gateway after a new SA was negotiated.</p>\n"
},
{
"id": "PAN-313850",
"summary": "Fixed an issue where a split-brain condition occurred and HA1/HA2 links went down while upgrading when the HA configuration used dataplane interfaces for HA1 and a combination of HSCI and Ethernet interfaces for HA2.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Fixed an issue where a split-brain condition occurred and HA1/HA2 links went down while upgrading when the HA configuration used dataplane interfaces for HA1 and a combination of HSCI and Ethernet interfaces for HA2.</p>\n"
},
{
"id": "PAN-313623",
"summary": "Fixed an issue where the /opt/pancfg/mgmt/ssl/private/ directory on Palo Alto Networks devices with TPM support became 100% utilized due to an accumulation of undeleted .pub_pem files. This occurred because executing the show device-certificate status CLI command initiated a process that generated these files but failed to remove them, which prevented the fetching of new device certificates.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Fixed an issue where the /opt/pancfg/mgmt/ssl/private/ directory on Palo Alto Networks devices with TPM support became 100% utilized due to an accumulation of undeleted .pub_pem files. This occurred because executing the show device-certificate status CLI command initiated a process that generated these files but failed to remove them, which prevented the fetching of new device certificates.</p>\n"
},
{
"id": "PAN-311285",
"summary": "Fixed an issue where a memory leak occurred related to the ospfd process, which caused RAM usage to continuously increase on active devices in an HA cluster until the device stopped responding, even after an HA failover.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Fixed an issue where a memory leak occurred related to the ospfd process, which caused RAM usage to continuously increase on active devices in an HA cluster until the device stopped responding, even after an HA failover.</p>\n"
},
{
"id": "PAN-308507",
"summary": "Fixed an issue where the firewall intermittently failed to maintain active log forwarding streams to Cortex Data Lake even when duplicate logging and enhanced application logging were enabled.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Fixed an issue where the firewall intermittently failed to maintain active log forwarding streams to Cortex Data Lake even when duplicate logging and enhanced application logging were enabled.</p>\n"
},
{
"id": "PAN-309300",
"summary": "Fixed an issue where management plane system resources configuration size exceeded 28 MB for over 4 hours, and the following error message was displayed: Configuration size reaching device capacity limit.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Fixed an issue where management plane system resources configuration size exceeded 28 MB for over 4 hours, and the following error message was displayed: Configuration size reaching device capacity limit.</p>\n"
},
{
"id": "PAN-302654",
"summary": "Fixed an issue where, when the HA configuration had multiple logical routers, static or connected routes redistributed into OSPF aged out in the LSDB, which caused the routes to be removed on peer OSPF neighbors.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Fixed an issue where, when the HA configuration had multiple logical routers, static or connected routes redistributed into OSPF aged out in the LSDB, which caused the routes to be removed on peer OSPF neighbors.</p>\n"
},
{
"id": "PAN-300423",
"summary": "Fixed an issue where Data Processing Cards (DPCs) installed in slots 5 and 6 remained stuck in a starting state with the error **Signal detected for port xeS5-DP0 but Link Down** alerts, which resulted in device instability.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Fixed an issue where Data Processing Cards (DPCs) installed in slots 5 and 6 remained stuck in a starting state with the error <strong>Signal detected for port xeS5-DP0 but Link Down</strong> alerts, which resulted in device instability.</p>\n"
},
{
"id": "PAN-298617",
"summary": "Optimized the commit workflow to reduce the size of the effective configuration, resulting in lower memory consumption.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Optimized the commit workflow to reduce the size of the effective configuration, resulting in lower memory consumption.</p>\n"
},
{
"id": "PAN-296202",
"summary": "Added a log enhancement to capture an issue where, when a commit operation was in progress, newly deployed IP address tags that used the XML API were not immediately reflected in address group resolution, which delayed IP address mapping to address groups and caused traffic to be incorrectly allowed or denied.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Added a log enhancement to capture an issue where, when a commit operation was in progress, newly deployed IP address tags that used the XML API were not immediately reflected in address group resolution, which delayed IP address mapping to address groups and caused traffic to be incorrectly allowed or denied.</p>\n"
},
{
"id": "PAN-273158",
"summary": "Fixed an issue where an incorrect ASIC configuration caused silent packet drops or application slowness when receiving a mix of jumbo and non-jumbo packets.",
"resolved": "",
"caveat": "",
"renderedHtml": "<p>Fixed an issue where an incorrect ASIC configuration caused silent packet drops or application slowness when receiving a mix of jumbo and non-jumbo packets.</p>\n"
}
]
test/issues-renderer.test.mjs
+49
View File
@@ -0,0 +1,49 @@
import assert from 'node:assert/strict';
import test from 'node:test';
import { readFileSync, readdirSync } from 'node:fs';
import { join } from 'node:path';
import { fileURLToPath } from 'node:url';
import { JSDOM } from 'jsdom';
const { window } = new JSDOM('<!doctype html><html><body></body></html>');
globalThis.DOMParser = window.DOMParser;
globalThis.fetch = () => Promise.resolve({
ok: true,
json: () => Promise.resolve([]),
text: () => Promise.resolve('')
});
const { parseMarkdownIssues, markdownSummaryToHtml } = await import('../web/js/issues.js');
const __dirname = fileURLToPath(new URL('.', import.meta.url));
const fixturesDir = join(__dirname, 'fixtures');
const fixtures = readdirSync(fixturesDir).filter(name => {
const contents = readdirSync(join(fixturesDir, name), { withFileTypes: true }).map(d => d.name);
return contents.includes('expected.md') && contents.includes('expected-parsed.json');
});
fixtures.forEach(fixtureId => {
const fixturePath = join(fixturesDir, fixtureId);
test(`parses and renders ${fixtureId}`, () => {
const markdownText = readFileSync(join(fixturePath, 'expected.md'), 'utf-8');
const expectedParsed = JSON.parse(readFileSync(join(fixturePath, 'expected-parsed.json'), 'utf-8'));
const parsed = parseMarkdownIssues(markdownText);
assert.equal(parsed.length, expectedParsed.length, 'issue count');
parsed.forEach((issue, i) => {
const expected = expectedParsed[i];
assert.equal(issue.id, expected.id, `issue[${i}] id`);
assert.equal(issue.summary, expected.summary, `issue[${i}] summary`);
assert.equal(issue.resolved, expected.resolved, `issue[${i}] resolved`);
assert.equal(issue.caveat, expected.caveat, `issue[${i}] caveat`);
const renderedHtml = markdownSummaryToHtml(issue.summary, issue.resolved, issue.caveat);
assert.equal(renderedHtml, expected.renderedHtml, `issue[${i}] renderedHtml`);
});
});
});
web/js/issues.js
+2 -2
View File
@@ -144,7 +144,7 @@ function fetchIssueFile(productKey, fileName, issueType) {
return request; return request;
} }
function parseMarkdownIssues(markdownText) { export function parseMarkdownIssues(markdownText) {
const input = String(stripMarkdownFrontmatter(markdownText) || ''); const input = String(stripMarkdownFrontmatter(markdownText) || '');
if (!input.trim()) { if (!input.trim()) {
return []; return [];
@@ -523,7 +523,7 @@ function normalizeSocialRefs(data) {
return map; return map;
} }
function markdownSummaryToHtml(summaryText, resolvedText, caveatText) { export function markdownSummaryToHtml(summaryText, resolvedText, caveatText) {
const input = String(summaryText || '').trim(); const input = String(summaryText || '').trim();
const resolved = String(resolvedText || '').trim(); const resolved = String(resolvedText || '').trim();
const caveat = String(caveatText || '').trim(); const caveat = String(caveatText || '').trim();