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.

In bug #1061646 new --interfacename option has been added to kickstart network command.
It can be used to specify name of vlan device if default form is not desired, eg because the resulting name is too long, exceeding IFNAMSIZE (the issue of this BZ).

The default form is
<PARENT>.<VLAN>
where <PARENT> is name of vlan's parent device (the device specified by network --device kickstart option) and <VLANID> is vlan id specified by network --vlanid kickstart option)

For example:

1)

network --device=em1 --bootproto=dhcp --vlanid=171 --activate

will create em1.171 vlan device

2)

network --device=00:15:17:96:75:0a --bootproto=dhcp --vlanid=171 --activate

will create em1.171 vlan device where em1 is name of device with MAC address 00:15:17:96:75:0a

3)

network --device=em1 --bootproto=dhcp --vlanid=171 --activate --interfacename=vlan171

will create vlan171 vlan device

Note: the option should be used (takes any effect) only when configuring vlan device, ie when --vlanid option is also present.

Hi, sorry for late update. We should add info from comment #17 bug #1081982 to the information about the new option.

(In reply to Radek Vykydal from comment #3)
> Hi, sorry for late update. We should add info from comment #17 bug #1081982
> to the information about the new option.

Added, too.

http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/Installation_Guide/index.html#sect-kickstart-commands

(In reply to Petr Bokoc from comment #4)

> http://documentation-devel.engineering.redhat.com/site/documentation/en-US/
> Red_Hat_Enterprise_Linux/7/html-single/Installation_Guide/index.html#sect-
> kickstart-commands

Thanks, it looks good but I have one remark to:

<cite>
* Names containing a dot (.) must take the form of DEVICE.ID - for example, em1.171. 
</cite>

Actually, as said in the bug 1081982 comment 17:

<cite>
- if it contains '.', vlan id should follow (eg 'ens7.171', 'mydev.171')
</cite>

the only constraint here is that vlan id must follow after the dot. The name before dot can be arbitrary, eg. the mydev.171 which is not clear to me from current doc. I think it is important to be clear as typical use case for the option is when device name is too long to fit into kernel size limit after vlan suffix (.171) is added so using the device name wouldn't work here.

So I'd write something like

* For names containing a dot (.) vlan id must follow after the dot - for example em1.171, my-vlan.171