-
Notifications
You must be signed in to change notification settings - Fork 48
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
fortios_router_route_map module does not attach ACL or prefix-list to it #3
Comments
hi @l0renzor , thanks for the issue.
from api server, I found the rule doesn't take effect at all:
so, the parameter is not filled right, I will take some to figure out the right parameters. thanks, |
I found
thanks to Jie's help, we found this one, but no fix yet. I will continue to find a workaround. |
Hey @chillancezen - I've been running in the same issue here. I think that this is a bug in the API. Did you already create a case to the fortinet support? |
depends on mantis #0667114 |
Issue Description
I cannot pass the match_ip_address attribute using the fortios_router_route_map.
The match_ip_address is not attached to the route-map resource. Other parameters like local_preference see working fine
Steps to reproduce
route_map.yaml
vars.yaml
run the play
ansible-playbook route_map.yaml
Actual and Expected result
The playbook ends with no errors, the route-map is created without the prefix-list attached.
the prefix-list has been configured manually
while the route-map does not contain the desired match_ip_address value
The text was updated successfully, but these errors were encountered: