Bug 682339

Summary:	assumes all network devices are named ethX or trX
Product:	Red Hat Enterprise Linux 6	Reporter:	Bill Nottingham <notting>
Component:	amtu	Assignee:	Steve Grubb <sgrubb>
Status:	CLOSED DUPLICATE	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1	CC:	ddumas, rvokal, sgrubb, syeghiay
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	682337	Environment:
Last Closed:	2012-05-14 15:51:53 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:
Bug Depends On:	682337
Bug Blocks:	682269

Description Bill Nottingham 2011-03-04 21:26:06 UTC

+++ This bug was initially created as a clone of Bug #682337 +++

Created attachment 482379 [details]
Patch... just read all devices with proper addresses

Description of problem:

Network devices can have arbitrary names, and due to http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming, will have different names in Fedora 15.

amtu assumes all devices are ethX or trX.

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

amtu-1.0.8

How reproducible:

Via source code inspection

Comment 2 RHEL Program Management 2011-03-04 21:58:04 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 4 RHEL Program Management 2011-07-06 01:32:49 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 8 Steve Grubb 2012-05-14 15:51:53 UTC


*** This bug has been marked as a duplicate of bug 689823 ***