Bug 762573 (GLUSTER-841) - Replacing a NIC should not show the old NIC information
Summary: Replacing a NIC should not show the old NIC information
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-841
Product: GlusterSP
Classification: Retired
Component: core
Version: unspecified
Hardware: All
OS: Linux
urgent
medium
Target Milestone: 3.1.2
Assignee: Timothy Asir
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-21 06:29 UTC by Raghavendra Bhat
Modified: 2010-12-15 12:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)
screen shot of the server manager table bond0 section when NIC was replaced (87.26 KB, image/png)
2010-04-21 03:36 UTC, Raghavendra Bhat
no flags Details

Description Raghavendra Bhat 2010-04-21 03:36:13 UTC
Created attachment 183 [details]
Patch to kernel spec to install cp patch and fix errant touch command.

Comment 1 Raghavendra Bhat 2010-04-21 03:36:36 UTC
Replacing a NIC will show the old NIC mac address also in the server manager table. i.e. in my situation NIC representing eth0 was replaced by another NIC. But in the server maager table of UI it shows still eth0 as the old NIC and the newly added NIC is represented by eth3. But since the bonding involved eth0 and eth2, I was not able to communicate with the server. The screenshot of the server manager table which explains this issue clearly is attached.

Comment 2 Raghavendra Bhat 2010-04-21 06:29:24 UTC

Comment 3 Raghavendra Bhat 2010-04-23 02:30:31 UTC
If a NIC is removed, then one cannot login to the platform. For the right password also it says invalid password. I can login through ssh and through the console on the first server.


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