- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
09-16-2011 06:44 AM
After an auto update of application we can't do a commit with out explanation on the commit page.
We discover that when we do a revert of application the commit is ok so we put off the auto update but we want it back.
How could we solve this problem ? Could it be possible to know which policy or application is concerned ?
Regards
09-17-2011 12:34 PM
the commit is failing ("commit failed" at the end) and there's dependency warning too :
but those dependency were ok befaure that, the commit is ok with the old application update
If I decide to update the applications and threats, the commit failed and didin't say why
I've no idea of which policy or application cause the fail
Regard
09-23-2011 12:54 AM
any idea ?
it's strange that anyone ever had the same problem
I've no particular policies or applications
I'll have to open a support case ...
10-31-2011 09:22 PM
I only see dependancy warnings so I'd have to request output from show jobs processed, specifically the job that failed. So dynami updates for content is still disabled at this point? What PANOS are you running? Did you eventually contact Support to open a case?
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!