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 1300755 - ifup network with an interface name with more than 16 characters
Summary: ifup network with an interface name with more than 16 characters
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.4
Hardware: Unspecified
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-21 16:05 UTC by steverweber
Modified: 2016-11-03 19:06 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 19:06:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2581 0 normal SHIPPED_LIVE Low: NetworkManager security, bug fix, and enhancement update 2016-11-03 12:08:07 UTC

Description steverweber 2016-01-21 16:05:47 UTC
Description of problem:

the new long style network device names are to long because vlans with 4 digits cause interface name to be > 15 chars 

you get the error: 

ifup eno33557248.3008
Error: argument "eno33557248.3008" is wrong: "name" too long

ERROR    : [/usr/sbin/ifup] ERROR: could not add vlan 3008 as eno33557248.3008 on dev eno33557248

NetworkManager also cant bring the interface up.

and `ip a` list the interface as "eno33557248.300" missing the 8



Steps to Reproduce:
1. create a network device with a vlan > 999 while using longer name format
2. (optional) disable NetorkManager
3. try and bring the interface online

Actual results:

Error: argument "eno33557248.3008" is wrong: "name" too long


Expected results:

all good

Comment 2 steverweber 2016-01-21 16:33:30 UTC
reported upstream to systemd
https://github.com/systemd/systemd/issues/2407

Comment 3 Thomas Haller 2016-01-21 17:51:09 UTC
As workaround, in NetworkManager you can configure the interface-name in the connection.

$ nmcli connection modify $CONNECTION_ID connection-interface vlan3008


Pushed a fix to upstream master:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=944065c1154a656846dcf37e1cce35d3fb1792ed
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=778207f23eb2ac022b2ee47968a484fdb94626fe


This only concerns NetworkManager. It is unrelated to using ifup with NetworkManager disabled.

Comment 5 Vladimir Benes 2016-08-30 10:04:54 UTC
NM now cuts name to fit the device name limitation (16) so long_device_name with vlan to 1024 is shortened from long_device_name.1024 to long_device_.1024 and everything works as expected.

Comment 7 errata-xmlrpc 2016-11-03 19:06:45 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://rhn.redhat.com/errata/RHSA-2016-2581.html


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