-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support for hip-profiles has been removed in 10.1.5 and 10.2.x, but panos still tries to put the hip-profiles
in security rules
#441
Comments
🎉 Thanks for opening your first issue here! Welcome to the community! |
PAN-OS 10.1.5-h1 Expected: Observed: Msg: |
### [1.7.2](v1.7.1...v1.7.2) (2022-04-27) ### Bug Fixes * **panos.base.PanObject.refresh_variable:** Refresh works again for regular and attrib style params ([#446](#446)) ([20dd7b7](20dd7b7)), closes [#444](#444) * **panos.policies.SecurityRule:** `hip-profiles` removed from v10.1.5+ ([#442](#442)) ([ab4d088](ab4d088)), closes [#441](#441)
This is fixed in 1.7.2 |
Patch in SDK 1.7.2 fixes the issue for PAN-OS 10.1.5+ |
Hi, the above issue was also observed on 11.0.2. how can we go ahead for resolution? |
How can I do a patch in SDK 1.7.2? do I have to replace the SDK version? |
Describe the bug
When using ansible or the panos python sdk to create security rules, the panos python sdk will add a default element of
hip-profiles
with the value ofAny
into the request xml. Such requests will fail on 10.1.5 and 10.2.x because support for thehip-profiles
element in security policies has been removed. This breaks all ansible playbooks that manage security policies on newer versions of panos. Yuck!Expected behavior
Security policies creation or updates should succeed without failure.
Current behavior
security policy creation and commits fail because of extraneous
hip-profiles
elements in the request xml.Possible solution
Modify versioning so that on version 10.1.5 and 10.2.x,
hip-profiles
elements are not submitted.Steps to reproduce
Your Environment
AWS vm-series firewall running PanOS 10.1.5 (we were afraid to upgrade to 10.2.0 because of the whole "you might lose your ip addresses from time-to-time" issue.
The text was updated successfully, but these errors were encountered: