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.

Bug 1493093

Summary:	rhel7 installation creates two network devices for just one network device
Product:	Red Hat Enterprise Linux 7	Reporter:	Supreet <srandhaw>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED NOTABUG	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	high
Version:	7.4	CC:	dracut-maint-list, harald, jkonecny, mbanas, mhruscak, mmatsuya, release-test-team-automation, srandhaw
Target Milestone:	rc
Target Release:	7.4
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1293539	Environment:
Last Closed:	2017-10-17 07:58:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1293539
Bug Blocks:

Comment 2 Supreet 2017-09-19 11:19:56 UTC

Case description :

The issue was resolved in RHEL7.3 but appears again in RHEL7.4. 

They installed RHEL7.4 and had the same issue in that ksdev0 was shown during the install rather than eth0 and at the end of the installation there was a ksdev0 device and not en0 as expected - there was an ifcfg-en0 file but the interface was not up and would not come up either.

Cmdline :
BOOT_IMAGE=/vmlinuz-3.10.0-693.1.1.el7.x86_64 root=/dev/mapper/rootvg-rootlv ro crashkernel=auto rd.lvm.lv=rootvg/rootlv rd.lvm.lv=rootvg/paginglv net.ifnames=0

Kickstart network line :
network --device=00:50:56:A1:13:B1 --bootproto=static --noipv6 --ip=10.245.8.20 --netmask=255.255.255.0 --gateway=10.245.8.1 --nameserver=10.125.97.176

In short, they are observing the interface as ksdev0 which pointed by them is similar to this Bugzilla

Comment 3 Jiri Konecny 2017-09-20 07:14:49 UTC

Hello Supreet,

Could the customer please provides us logs from the installation environment? Logs can be found in /tmp/*.log and syslog.

Thank you.

Comment 4 Supreet 2017-09-21 06:44:32 UTC

Hello Jiri,

I have requested the customer and will update you once I receive from them.

Regards,
Supreet Kaur