Palo Alto Networks | PAN-179420

The earliest recollection of this bug is traced back to PAN-OS 10.2.0 - May 16, 2024. This bug is fixed in PAN-OS versions 10.2.1. Fixed an issue on Panorama where a selective push to managed firewalls failed after renaming an existing device group, template, or template stack that was already pushed to the managed firewalls and you selectively committed specific configuration objects from the renamed device group, template, or template stack. On the Panorama management server, a selective push ( Commit Push to Devices Push Changes Made By and Commit Commit and Push Commit and Push Changes Made By to managed firewalls fails if you rename an existing device group, template, or template stack that was already pushed to your managed firewalls and you selectively committed specific configuration objects from the renamed device group, template, or template stack. Workaround: After you rename the existing device group, template, or template stack, Push ( Commit Push to Devices all configuration changes for the named device group, template, or template stack. For more information: https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-release-notes/pan-os-10-2-0-known-and-addressed-issues/pan-os-10-2-0-known-issues https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-release-notes/pan-os-10-2-1-known-and-addressed-issues/pan-os-10-2-1-addressed-issues