Panorama Commit issue 10.1.4-H4 after upgrade from 10.1.3

[paragkarki143]

Hi guys,

I have a Panorama- 10.1.4-H4 (upgraded from 10.1.3) on AWS and two other firewalls both at 10.0.9 on AWS.

After upgrading, Panorama, I cannot just commit. Throws an error saying  plugins unexpected here (for schema verification failed-reverted the config and when trying to commit after that gives the plugin error)

I see below difference in the candidate and running configs when validating (after reverting the config):

I do not see any bugs or any one else facing similar issue.

It looks like a corrupt candidate configuration. But I am afraid if I force commit/force commit it will affect the prod environment specially as it says in the validation process the plugins will be deleted.

Plugin for Panorama: 3.0.2

Plugin for Firewalls: 2.14

@BPry

@SteveCantwell 

@reaper 

Many Thanks,

[paragkarki143]

Hi Guys, 
Any chances you might be knowing the ans?
@BPry 
@SteveCantwell 

[SteveCantwell]

Howdy

I would think that if your company is not using plugins (please confirm) that you could delete the plugin(s) that are causing your issue.

[paragkarki143]

Hey @SteveCantwell,

Thanks for the reply. Unfortunately, the deployment is in AWS and the plugins are required. What may be the effect if I force commit (As I really think it's a case of a corrupt xml conf file  )? 

[SteveCantwell]

If you try a commit force and the running config is corrupted, you will still probably get an error and the commit will not be successful.

If you want, export your configuration off, and password protect it.  Attach to this thread and then PM directly with the password, then I will download it and try on my Panorama and see if I can figure it out. 😛  Always glad to assist the Community.