Bug 682339 - assumes all network devices are named ethX or trX
Summary: assumes all network devices are named ethX or trX
Keywords:
Status: CLOSED DUPLICATE of bug 689823
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: amtu
Version: 6.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Steve Grubb
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On: 682337
Blocks: 682269
TreeView+ depends on / blocked
 
Reported: 2011-03-04 21:26 UTC by Bill Nottingham
Modified: 2014-03-17 03:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 682337
Environment:
Last Closed: 2012-05-14 15:51:53 UTC
Target Upstream Version:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.