Bug 762544 (GLUSTER-812)

Summary: volumes are not started upon reboot after one of the interfaces are unselected from bonding
Product: [Retired] GlusterSP Reporter: Raghavendra Bhat <rabhat>
Component: coreAssignee: Balamurugan Arumugam <bala>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: unspecifiedCC: platform, webteam
Target Milestone: 3.0.4   
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 10:32:44 UTC
Sometimes it says none of the volumes have been started except one. But the actual situation is vice-versa. i.e. all but one volumes have been started.

Comment 1 Raghavendra Bhat 2010-04-08 10:35:49 UTC
There are 2 network interfaces(eth0 and eth1) in the first server. I unselected
one of the interfaces(tried both eth0 as wel as eth1) and configured it with a
separate IP address, and rebooted after updating the changes.But when the
server reboots the volumes are not started. Selecting all the volumes and giving start volume immedietly says none of the volumes are started. But most of the volumed are actually started except 2-3. Now selecting those non-started volumes and clicking start volume will also says that none of them have been started, whereas we can find that they have been started.