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.
DescriptionRyosuke Yasuoka
2020-05-28 04:44:02 UTC
Description of problem:
A warning message related to ipv6, "mtu: failure to set IPv6 MTU", is shown despite disabling ipv6 in the kernel boot parameter.
Version-Release number of selected component (if applicable):
# uname -r
4.18.0-193.el8.x86_64
NetworkManager-1.22.8-4.el8.x86_64
How to Reproduce:
It only happens when we configure VLAN.
Steps to Reproduce:
1. add kernel boot parameter "ipv6.disable=1"
2. configure vlan like below
# nmcli c add type vlan ifname enp1s0.195 con-name enp1s0.195 id 195 dev enp1s0 ipv4.method manual ipv6.method ignore ipv4.address 192.168.122.195/24
3. up enp1s0.195
# date; nmcli con up enp1s0.195
Thu May 28 00:33:27 EDT 2020
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/4)
4. the warning message is shown
# tail /var/log/messages
May 28 00:33:27 localhost NetworkManager[958]: <warn> [1590640407.9435] device (enp1s0.195): mtu: failure to set IPv6 MTU
May 28 00:33:27 localhost NetworkManager[958]: <info> [1590640407.9439] device (enp1s0.195): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
...
Expected results:
- We know that this warning message is NOT harmful and we can ignore it safely because the ipv6 is disabled correctly.
- I think this error message related to "ipv6" should not be shown while ipv6 is disabled in the kernel boot parameter.
Additional info:
At a glance at the source code of NetworkManager, I suspect that _commit_mtu() shows the warning message without checking the status of the kernel boot parameter, "ipv6.disable=1".
Comment 1Beniamino Galvani
2020-07-23 15:39:38 UTC
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 (NetworkManager bug fix and enhancement update), 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:4499