-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
rhel-system-roles-1.23.0-2.1.el8
-
None
-
Moderate
-
rhel-sst-system-roles
-
20
-
None
-
-
QE ack, Dev ack
-
False
-
-
Yes
-
None
-
Bug Fix
-
-
Done
-
None
What were you trying to do that didn't work?
The playbook fails while trying to add a ipv6 routing rule:
# cat net.yml | egrep routin -A4
routing_rule:
- priority: 5
from: '::/0'
iif: eth1
table: 1
The error message seems to point to `from` parameter which cannot be equal to `0`
[...] The full traceback is: File "/tmp/ansible_network_connections_payload_s4vo9dpf/ansible_network_connections_payload.zip/ansible/modules/network_connections.py", line 2760, in main File "/tmp/ansible_network_connections_payload_s4vo9dpf/ansible_network_connections_payload.zip/ansible/modules/network_connections.py", line 1850, in connections fatal: [192.168.77.53]: FAILED! => { [...] }, "msg": "fatal error: configuration error: connections[0].ip.routing_rule[0]: the prefix length for 'from' cannot be zero", "stderr": "\n", "stderr_lines": [ "" ] } PLAY RECAP ************************************************************************************************************************************************************************************************************************* 192.168.77.53 : ok=7 changed=0 unreachable=0 failed=1 skipped=9 rescued=0 ignored=0 # cat -n /usr/share/ansible/roles/rhel-system-roles.network/library/network_connections.py | egrep routing_rule.*from 1239 if routing_rule["from"]: 1242 routing_rule["from"]["address"], 1243 routing_rule["from"]["prefix"],
The command is fully supported by networkmanager:
# nmcli connection modify eth1 ipv6.routing-rules 'priority 5 from ::/0 table 1'
# nmcli connection up eth1
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/11)
# cat /etc/NetworkManager/system-connections/eth1.nmconnection | grep rule
routing-rule1=priority 5 from ::/0 table 1
Please provide the package NVR for which bug is seen:
# ansible-galaxy collection list | egrep rhel redhat.rhel_system_roles 1.21.2
How reproducible:
Always
Steps to reproduce
# dnf install redhat.rhel_system_roles -y 1. Example of playbook: --- - name: Configure the network with rhel system roles hosts: all become: true vars: network_connections: - name: eth1 type: ethernet autoconnect: true state: up ip: dhcp4: false address: - fd6d:8d64:af0c::2/64 gateway6: fd6d:8d64:af0c::1 route: - network: 'fd6d:8d64:af0c::' prefix: 64 table: 1 - network: '::' prefix: 0 gateway: 'fd6d:8d64:af0c::1' table: 1 routing_rule: - priority: 5 from: '::/0' iif: eth1 table: 1 - priority: 5 from: fd6d:8d64:af0c::/64 table: 1 roles: - rhel-system-roles.network ...
Expected results
# cat /etc/NetworkManager/system-connections/eth1.nmconnection | grep rule routing-rule1=priority 5 from ::/0 table 1
Actual results
The full traceback is: File "/tmp/ansible_network_connections_payload_s4vo9dpf/ansible_network_connections_payload.zip/ansible/modules/network_connections.py", line 2760, in main File "/tmp/ansible_network_connections_payload_s4vo9dpf/ansible_network_connections_payload.zip/ansible/modules/network_connections.py", line 1850, in connections fatal: [192.168.77.53]: FAILED! => { [...] }, "msg": "fatal error: configuration error: connections[0].ip.routing_rule[0]: the prefix length for 'from' cannot be zero", "stderr": "\n", "stderr_lines": [ "" ] } PLAY RECAP ************************************************************************************************************************************************************************************************************************* 192.168.77.53 : ok=7 changed=0 unreachable=0 failed=1 skipped=9 rescued=0 ignored=0
- clones
-
RHEL-1683 Ansible RHEL network system role issue with ipv6.routing-rules the prefix length for 'from' cannot be zero"
- Closed
- links to
-
RHEA-2023:124810 rhel-system-roles bug fix and enhancement update
- mentioned on