default
vr is created and assigned when configuring interfaces without vr
#535
Labels
bug
Something isn't working
Describe the bug
Running the
panos_interface
module and its related modules likepanos_aggregate_interface
for the first time creates adefault
vr, which gets associated with the interface.It also causes the task to always be
changed
on every run.Expected behavior
Virtual routers should be optional in Ansible when they're not required by the firewall.
A virtual router does not need to be specified (web shows
None
) to obtain a valid configuration when creating this configuration outside of Ansible.Current behavior
See description.
Possible solution
I don't think it's safe to skip the vr assignment when
vr_name
is set to an empty string (equivalent toNone
when passed to the module) without breaking backwards compatibility.I'm not sure if there's a good solution for this other than exposing this through a new parameter to explicitly not assign it to a vr.
Steps to reproduce
Screenshots
Context
I'm trying to create an interface without vr assignment.
This interface will have subinterfaces on vlans with associated virtual routers, but the parent interface should not have a vr assigned.
I could not find a viable workaround for devices where the limit of virtual routers is already reached, as the entire task will fail due to it being unable to create a new
default
zone.The only way to deal with this for now seems to be explicitly assigning the interfaces to a vr they don't really belong to.
Your Environment
pan-os-python==1.11.0
pan-python==0.17.0
The text was updated successfully, but these errors were encountered: