[FIREWALL] - Commit Issue

lucas.nascimento — Tue, 19 May 2026 16:44:55 GMT

Hi everyone, I'd like to request support for a recent problem I'm having. I have one cluster with two Palo Alto firewalls, one of which was recently updated to version 11.1.13-h5 and is currently active, while the other is on version 11.1.13 and is passive. The environment is currently in this state because we are still validating version 11.1.13-h5 and will update the other member later.

In short, the commit test worked after the update and is synchronized with the other member. However, today when I try to commit any policy change, object change, etc., the commit is not applied and remains at 0%.

If I make a new commit, the job remains in the queue and also doesn't progress beyond 0%.

I used the 'show jobs all' command and confirmed that there are many pending jobs.

Via the GUI, I also tried running 'Clear Commit Queue' and received an error message saying 'Error removing jobs from queue'.

I also tried 'revert config', but it had no effect.

I haven't rebooted yet because I'd like to resolve the issue without doing so and collect data to help with troubleshooting.

Has anyone else experienced this problem?

topic [FIREWALL] - Commit Issue in Next-Generation Firewall Discussions

[FIREWALL] - Commit Issue