Bug 965842

Summary: network device configuration named 'Boot Disk'
Product: [Fedora] Fedora Reporter: Bill Nottingham <notting>
Component: dracutAssignee: dracut-maint
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dracut-maint, dshea, g.kaviyarasu, harald, jonathan, mkolman, rvokal, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: dracut-027-81.git20130531.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-02 03:01:07 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:

Description Bill Nottingham 2013-05-21 20:25:06 UTC
Description of problem:

Did a virt install over HTTP. My ifcfg-eth0 contains:

NAME="Boot Disk"

Even if the install was done via downloading kernel/boot images over network, that seems an odd name.

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

20130521 nightly

How reproducible:

once so far

Steps to Reproduce:
1. Install with virt-manager
2. Look at ifcfg-eth0

Comment 1 Brian Lane 2013-05-22 00:38:31 UTC
Please attach the logs as individual text/plain files.

Comment 2 Radek Vykydal 2013-05-22 11:01:14 UTC
The name is set by dracut generating the ifcfg file.

Just for information, in anaconda we use device name as NAME of a connection when dumping ifcfg files for connections created automatically by NM, eg we rename "Wired Connection 1" to "eth0" so that the dumped file is named ifcfg-eth0 instead of ifcfg-Wired_Connection_1).

Comment 3 Bill Nottingham 2013-05-22 18:03:51 UTC
So this is a dracut bug? I note that if I have multiple adapters, they all get 'Boot Disk' set for NAME.

Comment 4 Harald Hoyer 2013-05-28 14:54:10 UTC
Oh :) that name was copied and pasted since at least 4 years (git blame for the rescue :) ... 
apparently nobody has used the ifcfg-* files since then :)

Comment 5 Harald Hoyer 2013-05-28 14:57:22 UTC
commit 284d62da816a9d3678906e9dbeb796132016b9c9

Comment 6 Fedora Update System 2013-05-31 08:23:14 UTC
dracut-027-81.git20130531.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/dracut-027-81.git20130531.fc19

Comment 7 Fedora Update System 2013-05-31 18:08:50 UTC
Package dracut-027-81.git20130531.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dracut-027-81.git20130531.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-9728/dracut-027-81.git20130531.fc19
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2013-06-02 03:01:07 UTC
dracut-027-81.git20130531.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.