Bug 174110

Summary:	hardware device association is displyed incorrectly.
Product:	[Fedora] Fedora	Reporter:	David Bentley <david.r.bentley>
Component:	system-config-network	Assignee:	Harald Hoyer <harald>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-11-26 18:01:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Bentley 2005-11-24 17:15:33 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.7.10) Gecko/20050811 Fedora/1.7.10-1.1.1.legacy

Description of problem:
I have two network devices available which are associated correctly when you look
at the network script files ifcfg-eth0 and ifcfg-eth1.

But under the hardware tab they are associated incorrectly/differently and also 
when you edit a higlighted device in the devices tab and then look at hardware
they are again associated incorrectly/differently.

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

How reproducible:
Always

Steps to Reproduce:
see description

Actual Results:  Harware tab shows the following :-

Intel Corporation 82557/8/9 [Ethernet Pro 100] as eth1
Intel Corporation 8254OEM Gigabit Ethernet Controller as eth0

Expected Results:  As attributed in the network scripts

Intel Corporation 82557/8/9 [Ethernet Pro 100] as eth0
Intel Corporation 8254OEM Gigabit Ethernet Controller as eth1

Additional info:

These two devices are situated on the Intel SE7505VB2 motherboard and the only
one currently in use (connected to anything) is the 82557/8/9 [Ethernet Pro 100]

Comment 1 David Bentley 2005-11-25 00:20:58 UTC

Problem now resolved after doing all updates but I don't know which update
fixed this problem as the system-config-network has not been updated.

I will keep a eye on things to see if anything changes before closing this bug.

Comment 2 David Bentley 2005-11-26 18:01:13 UTC

I think it all sorted itself out when I used system-config-network to disable my 
unused network interface at startup (Intel Corporation 8254OEM Gigabit Ethernet
Controller) so i will now close this bug report as NOTABUG.