Bug 81398 - r-c-n will fail when on hw. addr dialog w/ multiple NIC's
Summary: r-c-n will fail when on hw. addr dialog w/ multiple NIC's
Status: CLOSED DUPLICATE of bug 59017
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: 4Suite
Version: 2.1
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2003-01-08 23:55 UTC by Mike Gahagan
Modified: 2008-05-01 15:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-02-21 18:51:02 UTC
Target Upstream Version:

Attachments (Terms of Use)
r-c-n traceback (3.76 KB, text/plain)
2003-01-08 23:59 UTC, Mike Gahagan
no flags Details

Description Mike Gahagan 2003-01-08 23:55:43 UTC
Description of problem:

(reported to me by AS Base customer, info in attachment)

r-c-n will crash w/ traceback when using the hardware device dialog to probe for
the MAC address

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

on AS 2.1

How reproducible:

Can be reproduced every time by customer, I can't reproduce it at all on a box
w/ 1 nic.. the only AS box I have to test with right now.

Steps to Reproduce:
1. start r-c-n
2. select a device under devices (eth0 etc.)
3. click edit
4. click hw. device tab
5. check "Use hardware address"
6. click "probe for address" (this shows the correct MAC address)
7. click ok
8. click apply (main window)
9. get traceback
Actual results:

see attached

Expected results:

r-c-n should not crash

Additional info:

see attachment.

Comment 1 Mike Gahagan 2003-01-08 23:59:11 UTC
Created attachment 89227 [details]
r-c-n traceback

my guess is ocfs (Oracle's cluster fs) is tainting the kernel, I doubt its
really an issue.. failure occurs regardless of which NIC is used.

Comment 2 Harald Hoyer 2003-01-09 09:48:15 UTC

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

Comment 3 Red Hat Bugzilla 2006-02-21 18:51:02 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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