'HA Group 1: Running configuration not synchronized after failure'

[myky]

Hi All,

I guess it is expected for the device to throw the error message below:

Thanks,

Myky

[reaper]

would need a little more context

did a local commit fail due to an error? in which case it is expected the (failed) config is not synced

[myky]

How can l check that? 

There was a commit lock, just 7 seconds before this alert was triggered:

Thanks,

Myky

[reaper]

if the system log is not providing more details you could check the jobs/tasks or the ms.log for more details

[myky]

Hi @reaper 

Not sure how to interpret this:

[reaper · Accepted solution]

not entirely sure, you'll want to take a look at the peer's ms.log and compare what is happening on both sides

[myky]

Hi again guys,

Logs from the spare unit don't mean much to me:

This was a one-time instance. If it occurs again we will get TAC involved.

Thanks again,

Myky

[Fariq_Zaidi]

Hi Myky,

Did the issue re-occur?  Did you have open to TAC and what the solution?
For now workaround is to manually sync from Panorama to firewall but we don’t want to do always. This will not be the best practice.

if have the solution can you share ?

Thank you

Regards

Fariq

[jasonwald]

I have this same thing happen since 10.2 on may models of hardware when pushing from Panorama down to the firewalls. Interesting part is by the time I login to the firewalls locally they show sync'd so very confused by the error.

So it is annoying but appears to be pretty benign for us.