Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
- Customer found that when they configured a static ipv6 route for a vlan into the network manager, they realized that in the ipv6 routing table, a digit in the last hextet does not appear as you can se in the log, so the ping failed:
this route we configured into the networ manager:
2806:219:9:30c1:b46:c1:9a9:7ac/127 2806:219:9:30c1:b46:c1:9a9:6ac
- The route that they can see after :c1 appers just "a9" and it has to be "9a9"
[root@t_dhcp_valle_mty01 ~]# route -n -A inet6
Kernel IPv6 routing table
Destination Next Hop Flag Met Ref Use If
2806:219:9:30c1:b46:c1:a9:7ac/127 2806:219:9:30c1:b46:c1:9a9:6ac UG 401 0 0 SVI_Cluster_101
^^^
Customers workaround to solve the problem, they commited the full static route ipv6 address via command line as you can see:
/sbin/ip -6 route add 2806:0219:0009:30c1:0b46:00c1:09a9:07ac/127 via 2806:0219:0009:30c1:0b46:00c1:09a9:06ac metric 1
- Afterwards, the pings are successfull but the problem that they face now is with this configuration, the static ipv6 route is not persistant. As soon as they restart the daemon "network services" or the server is reloaded they lose the configuration.
=========== REPRODUCED BELOW ===========
Test in VM gets the same results:
# grep IPV6 ifcfg-ens13
IPV6INIT=yes
IPV6_AUTOCONF=no
IPV6_DEFROUTE=no
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
IPV6ADDR=2806:219:9:30c1:b46:c1:9a9:6ad/127
# cat -v route6-ens13
2806:219:9:30c1:b46:c1:9a9:7ac/127 via 2806:219:9:30c1:b46:c1:9a9:6ac metric 1
# ip -6 route show | grep b46
2806:219:9:30c1:b46:c1:a9:7ac/127 via 2806:219:9:30c1:b46:c1:9a9:6ac dev ens13 proto static metric 1 pref medium
2806:219:9:30c1:b46:c1:9a9:6ac/127 dev ens13 proto kernel metric 100 pref medium
When I remove the route6-ens13 and use IPV6_DEFAULTGW=2806:219:9:30c1:b46:c1:9a9:6ac in the ifcfg-ens13 the 9 isn't dropped.
With the route6-ens13 file in place, and ifcfg-ens13 containing NM_CONTROLLED=no, this issue doesn't occur. Therefore this is a NetworkManager bug.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:1162
- Customer found that when they configured a static ipv6 route for a vlan into the network manager, they realized that in the ipv6 routing table, a digit in the last hextet does not appear as you can se in the log, so the ping failed: this route we configured into the networ manager: 2806:219:9:30c1:b46:c1:9a9:7ac/127 2806:219:9:30c1:b46:c1:9a9:6ac - The route that they can see after :c1 appers just "a9" and it has to be "9a9" [root@t_dhcp_valle_mty01 ~]# route -n -A inet6 Kernel IPv6 routing table Destination Next Hop Flag Met Ref Use If 2806:219:9:30c1:b46:c1:a9:7ac/127 2806:219:9:30c1:b46:c1:9a9:6ac UG 401 0 0 SVI_Cluster_101 ^^^ Customers workaround to solve the problem, they commited the full static route ipv6 address via command line as you can see: /sbin/ip -6 route add 2806:0219:0009:30c1:0b46:00c1:09a9:07ac/127 via 2806:0219:0009:30c1:0b46:00c1:09a9:06ac metric 1 - Afterwards, the pings are successfull but the problem that they face now is with this configuration, the static ipv6 route is not persistant. As soon as they restart the daemon "network services" or the server is reloaded they lose the configuration. =========== REPRODUCED BELOW =========== Test in VM gets the same results: # grep IPV6 ifcfg-ens13 IPV6INIT=yes IPV6_AUTOCONF=no IPV6_DEFROUTE=no IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy IPV6ADDR=2806:219:9:30c1:b46:c1:9a9:6ad/127 # cat -v route6-ens13 2806:219:9:30c1:b46:c1:9a9:7ac/127 via 2806:219:9:30c1:b46:c1:9a9:6ac metric 1 # ip -6 route show | grep b46 2806:219:9:30c1:b46:c1:a9:7ac/127 via 2806:219:9:30c1:b46:c1:9a9:6ac dev ens13 proto static metric 1 pref medium 2806:219:9:30c1:b46:c1:9a9:6ac/127 dev ens13 proto kernel metric 100 pref medium When I remove the route6-ens13 and use IPV6_DEFAULTGW=2806:219:9:30c1:b46:c1:9a9:6ac in the ifcfg-ens13 the 9 isn't dropped. With the route6-ens13 file in place, and ifcfg-ens13 containing NM_CONTROLLED=no, this issue doesn't occur. Therefore this is a NetworkManager bug.