"Bad template push candidate on disk"

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

"Bad template push candidate on disk"

L1 Bithead

Good Afternoon Everyone, 

 

I will start off with, I am very new to Palo Alto and I just want to make sure I don't jack anything up in my production environment. I got the following message when trying to push a change to one of my firewalls today: "Bad template push candidate on disk". I have done some research and it appears the following is the corrective action: 

 

Resolution
Follow the below steps to resolve the issue:

  1. Removed the firewall from the Template-Stack
  2. Commit on the Panorama.
  3. Re-added the Firewall to the same Template-Stack.
  4. Commit on the Panorama.
  5. Then pushed the Template to the firewalls.

My question is, what impact will this have on the firewall itself. When I take the firewall out of the template stack will it still continue to function with the current configuration that it has? When I add the firewall back to the template stack and do a commit, does this have the potential to cause an outage? I just want to make sure if this is going to take down the environment in any way I make the necessary request for an outage.  

2 accepted solutions

Accepted Solutions

Cyber Elite
Cyber Elite

Hello @anthonywadmin

 

it looks like you are referring to this KB. These steps will not case any outage. Steps 1 to 4 are performed within Panorama with commit to Panorama only. Until you get to step no.5 the configuration is not going to be pushed to managed Firewall. It is safe to perform these steps without outage.

 

Kind Regards

Pavel

Help the community: Like helpful comments and mark solutions.

View solution in original post

L1 Bithead

Pavel thank you for the support. I really appreciate it. 

View solution in original post

4 REPLIES 4

Cyber Elite
Cyber Elite

Hello @anthonywadmin

 

it looks like you are referring to this KB. These steps will not case any outage. Steps 1 to 4 are performed within Panorama with commit to Panorama only. Until you get to step no.5 the configuration is not going to be pushed to managed Firewall. It is safe to perform these steps without outage.

 

Kind Regards

Pavel

Help the community: Like helpful comments and mark solutions.

L1 Bithead

Pavel thank you for the support. I really appreciate it. 

L0 Member

Hi 

I am working on a case for one of our clients who is experiencing this same problem.

Reviewing the KB https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PPj9CAG we see that this is exposed for PAN-OS versions 8.1 and 9.0.

Do you know if this is also valid for higher versions?

Thank you very much in advance

Agustin my firewalls running into this issue were running "PAN-OS 10.6.1-h3". I followed the procedures in the KB and it resolved my issue. 

  • 2 accepted solutions
  • 1900 Views
  • 4 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!