Skip to content
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

paloaltonetworks.panos.panos_static_route on 2.21.2 #584

Closed
patsilvafox opened this issue Sep 26, 2024 · 4 comments · Fixed by #589
Closed

paloaltonetworks.panos.panos_static_route on 2.21.2 #584

patsilvafox opened this issue Sep 26, 2024 · 4 comments · Fixed by #589
Assignees
Labels
bug Something isn't working

Comments

@patsilvafox
Copy link

Describe the bug

while creating a static route that has the nexthop_type as 'none' the playbook fails that the an empty value on nexthop is not allowed. Further the documentation seems also misleading, as it says: "Next hop IP address. Required if state=present." This shouldn't be the case for nexthop_type: 'none'.

Expected behavior

On version 2.20.0 it works as expected.

Current behavior

Error: Failed create: to_Users_10.14.27.248_29 -> nexthop is invalid"

Possible solution

Enforcing the 2.20 collection get it back to a working state.

Steps to reproduce

Task:
paloaltonetworks.panos.panos_static_route:
provider: '{{ provider }}'
template: '{{ template_name }}'
virtual_router: '{{ vr_router_datacenter }}'
name: 'to_Users_{{ route_name }}'
destination: '{{ user_network }}'
interface: '{{ int_tunnel }}'
nexthop_type: 'none

Screenshots

Context

Your Environment

  • Collection: 2.21.2
  • Python:
  • Ansible:
  • PAN-OS Python Library & version (e.g. pandevice 0.14.0, pan-os-python 1.0.2):
@patsilvafox patsilvafox added the bug Something isn't working label Sep 26, 2024
@alperenkose alperenkose self-assigned this Oct 10, 2024
@alperenkose alperenkose linked a pull request Oct 10, 2024 that will close this issue
4 tasks
@alperenkose
Copy link
Collaborator

We have a draft PR that will resolve this issue however it depends on a change in pan-os-python. We need to wait for pan-os-python PR to be merged before merging this.

@laxman356
Copy link

do we have any update on this? Even I'm facing the same issue. Do I need to wait for the PR to be approved and merged or do we have any alternate solution that I can apply?

@alperenkose
Copy link
Collaborator

we have an alternative solution to this now on #589 which doesn't depend on pan-os-python, we will have this merged soon.

@alperenkose
Copy link
Collaborator

This has been fixed in currently released version 2.21.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
3 participants