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.
Bug 1637853 - failed to disable userspace IPv6LL address handling
Summary: failed to disable userspace IPv6LL address handling
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.5
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-10 08:28 UTC by Muneaki Sugaya
Modified: 2021-12-10 17:52 UTC (History)
9 users (show)

Fixed In Version: NetworkManager-1.18.0-0.3.20190408git43d9187c14.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 13:16:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2797011 0 None None None 2018-10-23 08:10:46 UTC
Red Hat Product Errata RHBA-2019:2302 0 None None None 2019-08-06 13:16:45 UTC

Description Muneaki Sugaya 2018-10-10 08:28:29 UTC
Description of problem:

NetworkManager logs the following on ipv6 disabled system.

~~~
failure changing link: failure 97 (Address family not supported by protocol)
failed to disable userspace IPv6LL address handling (unspecified)
~~~


Version-Release number of selected component (if applicable):

NetworkManager-1.10.2-16.el7_5


How reproducible:
Always


Steps to Reproduce:
- Sample
1. Set a kernel parameter, ipv6.disable=1

2. nmcli con add con-name ens8 type ethernet ifname ens8 ipv4.addresses 172.16.1.10/24 ipv4.method manual ipv6.method ignore

3. nmcli con down ens8; nmcli con up ens8

4. Get the following message.

~~~
NetworkManager[3214]: <warn>  [1539139755.3003] platform-linux: do-change-link[3]: failure changing link: failure 97 (Address family not supported by protocol)
NetworkManager[3214]: <warn>  [1539139755.3003] device (ens8): failed to enable userspace IPv6LL address handling (unspecified)
~~~


Actual results:

See the message


Expected results:

Do not see the message


Additional info:

Comment 4 Filip Pokryvka 2019-04-08 14:05:10 UTC
Tested, messages have correct log level now, Sanity Only since we are not able to test with ipv6.disable=1 in our CI.

Comment 6 errata-xmlrpc 2019-08-06 13:16:24 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, 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-2019:2302


Note You need to log in before you can comment on or make changes to this bug.