The commit is successful, but the configuration remains on the candidate and so cannot be pushed to the device.
Bug since upgrade Panorama in 11.x
Issue at least on Panorama version
11.0.4-h2
11.1.2-h4
11.1.2-h3
11.1.3-h1
No issue on 10.2.8, was working fine for months.
Expected behavior
Commit the configuration to the running of the panorama
Current behavior
The rule is well created on the Panorama but the commit does not fully commit the rule.
The panorma thinks that everything is committed because the commit was successful but the configuration remained in the candidate.
Possible solution
Steps to reproduce
Create an item in a DG, for example a rule with paloaltonetworks.panos.panos_security_rule
Commit with paloaltonetworks.panos.panos_commit_panorama
Check if there is commit waiting in Panorama (normally no)
Preview changes on commit to panorama (the changes will be in candidat)
Describe the bug
The commit is successful, but the configuration remains on the candidate and so cannot be pushed to the device.
Bug since upgrade Panorama in 11.x Issue at least on Panorama version 11.0.4-h2 11.1.2-h4 11.1.2-h3 11.1.3-h1
No issue on 10.2.8, was working fine for months.
Expected behavior
Commit the configuration to the running of the panorama
Current behavior
The rule is well created on the Panorama but the commit does not fully commit the rule. The panorma thinks that everything is committed because the commit was successful but the configuration remained in the candidate.
Possible solution
Steps to reproduce
The rule pushed
The commit task
I have tried without and with force:true, but no difference
Screenshots
Context
Your Environment