Bug 762541 (GLUSTER-809)

Summary: changing the IP address in bonding leads to unresponding ejabberd
Product: [Retired] GlusterSP Reporter: Raghavendra Bhat <rabhat>
Component: coreAssignee: Balamurugan Arumugam <bala>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: unspecifiedCC: platform, shireesh, webteam
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Raghavendra Bhat 2010-04-08 07:09:33 UTC
Just changing the IP address of the bonding will create problem. It says the system is rebooting in 15 seconds, but the system does not reboot. Have to login using ssh and doing manually reboot there will make things proper.

Comment 1 Raghavendra Bhat 2010-04-08 09:19:42 UTC
There were two network interfaces eth0 and eth1. I bonded them together with IP address of the bond as the one present int the general tab. Then I removed eth0 from the bond gave it separate IP address different from the general section. It worked well. Then again included it in bond0 and gave bind0 a different IP address. But after rebooting it doesnot take the password. It says invalid password for the right password also, hence not able to login. But can login through ssh.