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.
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: 'toUsers{{ route_name }}' destination: '{{ user_network }}' interface: '{{ int_tunnel }}' nexthop_type: 'none
1. 2. 3. 4.
Screenshots
Context
Your Environment