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 1293539 - rhel7 instalation creates two network devices for just one network device
Summary: rhel7 instalation creates two network devices for just one network device
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.2
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Jiri Konecny
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1493093
TreeView+ depends on / blocked
 
Reported: 2015-12-22 05:25 UTC by Masahiro Matsuya
Modified: 2019-12-16 05:13 UTC (History)
7 users (show)

Fixed In Version: anaconda-21.48.22.60-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1493093 (view as bug list)
Environment:
Last Closed: 2016-11-03 23:21:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:2158 0 normal SHIPPED_LIVE anaconda bug fix and enhancement update 2016-11-03 13:13:55 UTC

Description Masahiro Matsuya 2015-12-22 05:25:01 UTC 
Description of problem:
A customer saw a problem that two network devices were activated for just one network device in RHEL7.2 installation. And, I could reproduce the problem with the following boot pameters.
  
   ks=file:/ks.cfg ifname=provisioning:52:54:00:48:8b:3f bootdev=provisioning ip=provisioning:dhcp

 -> rename the network device with 52:54:00:48:8b:3f into "provisioning"
 -> kickstart file "ks.cfg" is in the local.

And, the kickstart has the following network command.

   network --device 52:54:00:48:8b:3f --bootproto dhcp --noipv6

This network command is for the same network device specified in the boot parameter.

In this case, kickstart is parsed in dracut-cmdline hook, and the network devices are not avialable at that time. So, it cannot find the network device with 52:54:00:48:8b:3f, and it named it 'ksdev0' as another network device.
This causes to create wait-ksdev0.sh in initqueue/finished, and it never finish since such a device doesn't exist in the system.

I thought the kickstart file should be parsed in initqueue even if it's in initrd.img.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 7.2

How reproducible:
Always

Steps to Reproduce:
1. create kickstart file with the following network command.

network --device 52:54:00:48:8b:3f --bootproto dhcp --noipv6

 NOTE: use a proper MAC address in the test machine

2. locate the kickstat file into initrd.img of rhel7.2 as /ks.cfg
3. rebuild rhel7.2 installation iso with the initrd.img
4. use this boot parameter

  ks=file:/ks.cfg ifname=provisioning:52:54:00:48:8b:3f bootdev=provisioning ip=provisioning:dhcp

 NOTE: use a proper MAC address. use a proper nameserver IP address

5. and start rhel7.2 installation 

Actual results:
The installation stops in initqueue phase, since it never see ksdev0.

Expected results:
The device speicifed in boot paramter and one specified in kickstart is recognized as just one network device with the name specfied in boot paramter 'provisioning'.
Comment 1 Harald Hoyer 2016-01-07 10:18:08 UTC 
hmm, ksdev0 is wanted by the anaconda dracut part.
Comment 11 errata-xmlrpc 2016-11-03 23:21:13 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/RHEA-2016-2158.html
Note You need to log in before you can comment on or make changes to this bug.