Bug 762405 (GLUSTER-673)

Summary: First server can be shutdown by refreshing the machine connected to it
Product: [Retired] GlusterSP Reporter: Raghavendra Bhat <rabhat>
Component: coreAssignee: Balamurugan Arumugam <bala>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0.3CC: fharshav, 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-02-23 06:09:11 UTC 
Connect to the first server(i.e the management server) from a remote machine through browser(ex:http://192.168.1.35 connects to 192.168.1.35 which is the management server).We will get the webUI in the remote machine. If we click reboot then the mangement server reboots. Immedietly after clicking reboot, if we click shutdown it will ask wherther we want to shutdown. Clicking "ok", then waiting till the management server boots and immedietly after it reboots when we are about to get the login screen, refreshing in the remote machine will shutdown the management server(since we had clicked shutdown immedietly after clicking reboot). Not only shutdown, immedietly after clicking reboot  whatever we had clicked that thing will be activated when we refresh in the remote machine after the management server reboots.
Comment 1 Harshavardhana 2010-03-10 10:33:15 UTC 
Until distributed management comes slave node installation will have "httpd" switched off, fixed upstream in 3.0.4 branch
Comment 2 Harshavardhana 2010-03-24 00:46:43 UTC 
Raghavendra are you still able to reproduce this?